Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1309032
| From | Wei Ni <wni@nvidia.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH V1 02/10] thermal: tegra: combine sensor group-related data |
| Date | 2016-01-14 06:50 +0100 |
| Message-ID | <qQIXf-2y1-5@gated-at.bofh.it> (permalink) |
| References | <qQovv-4Vo-3@gated-at.bofh.it> <qQovx-4Vo-17@gated-at.bofh.it> <qQuKB-11D-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 2016年01月13日 22:31, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Wed, Jan 13, 2016 at 03:58:41PM +0800, Wei Ni wrote:
>> Combine sensor group-related data structures into struct
>> tegra_tsensor_group. This provides a single location for
>> sensor group data storage.
>> More sensor group data will be added in subsequent patches.
>>
>> Get rid of T124-specific PDIV/HOTSPOT hack.
>> tegra-soctherm.c contained a hack to set the SENSOR_PDIV and
>> SENSOR_HOTSPOT_OFFSET registers - it just did two writes of
>> T124-specific opaque values. Convert these into a form that can be
>> substituted on a per-chip basis, and into structure fields that have
>> at least some independent meaning.
>
> This reads as two completely separate commit messages. Should the patch
> be split up to separate out the two logical changes?
Hmm, you are right, will do it.
>
>> diff --git a/drivers/thermal/tegra/tegra_soctherm.c b/drivers/thermal/tegra/tegra_soctherm.c
> [...]
>> +static struct tegra_tsensor_group tegra124_tsensor_group_cpu = {
> [...]
>> +};
>> +
>> +static struct tegra_tsensor_group tegra124_tsensor_group_gpu = {
> [...]
>> +};
>> +
>> +static struct tegra_tsensor_group tegra124_tsensor_group_pll = {
> [...]
>> +};
>> +
>> +static struct tegra_tsensor_group tegra124_tsensor_group_mem = {
> [...]
>> +};
>> +
>> +static struct tegra_tsensor_group *
>> +tegra124_tsensor_groups[TEGRA124_SOCTHERM_SENSOR_NUM] = {
> [...]
>> };
>
> These look like they should all be static const.
Yes, they should be "static const", I fixed them in the next patch [03/10].
I will change it in this patch.
>
>> @@ -168,7 +268,7 @@ struct tegra_soctherm {
>> struct clk *clock_soctherm;
>> void __iomem *regs;
>>
>> - struct thermal_zone_device *thermctl_tzs[4];
>> + struct thermal_zone_device *thermctl_tzs[TEGRA124_SOCTHERM_SENSOR_NUM];
>> };
>
> Does it make sense to use macros here for the number of zones? I suspect
> that since you do parameterize the Tegra210 support that will be added
> later on will have a different maximum number, in which case macros will
> not work very well.
All the Tegra serial chips support 4 thermal zones: cpu, gpu, mem, pllx,
including the Tegra 210, so we can use the TEGRA124_SOCTHERM_SENSOR_NUM.
>
> But perhaps I'll see how you solved that problem in a later patch.
>
> Thierry
>
> * Unknown Key
> * 0x7F3EB3A1
>
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH V1 00/10] Add T210 support in tegra_soctherm Wei Ni <wni@nvidia.com> - 2016-01-13 09:00 +0100
[PATCH V1 02/10] thermal: tegra: combine sensor group-related data Wei Ni <wni@nvidia.com> - 2016-01-13 09:00 +0100
Re: [PATCH V1 02/10] thermal: tegra: combine sensor group-related data Thierry Reding <thierry.reding@gmail.com> - 2016-01-13 15:40 +0100
Re: [PATCH V1 02/10] thermal: tegra: combine sensor group-related data Wei Ni <wni@nvidia.com> - 2016-01-14 06:50 +0100
csiph-web