From: Wei Ni <wni@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: <rui.zhang@intel.com>, <MLongnecker@nvidia.com>,
<swarren@wwwdotorg.org>, <mikko.perttunen@kapsi.fi>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3 05/11] thermal: tegra: add T210-specific SOC_THERM driver
Date: Mon, 25 Jan 2016 13:48:43 +0800 [thread overview]
Message-ID: <56A5B73B.6040706@nvidia.com> (raw)
In-Reply-To: <20160121142546.GA32301@ulmo>
On 2016年01月21日 22:25, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Mon, Jan 18, 2016 at 06:03:46PM +0800, Wei Ni wrote:
>> Add Tegra210 specific SOC_THERM driver.
>>
>> Signed-off-by: Wei Ni <wni@nvidia.com>
>> ---
>> drivers/thermal/tegra/Makefile | 1 +
>> drivers/thermal/tegra/soctherm-fuse.c | 11 ++
>> drivers/thermal/tegra/soctherm.c | 6 +
>> drivers/thermal/tegra/soctherm.h | 4 +
>> drivers/thermal/tegra/tegra210-soctherm.c | 181 ++++++++++++++++++++++++++++++
>> 5 files changed, 203 insertions(+)
>> create mode 100644 drivers/thermal/tegra/tegra210-soctherm.c
>
> This looks pretty good, just a few minor nits...
>
>> diff --git a/drivers/thermal/tegra/soctherm.h b/drivers/thermal/tegra/soctherm.h
> [...]
>> index 1ac66cafb392..bd0f03bc9d80 100644
>> --- a/drivers/thermal/tegra/soctherm.h
>> +++ b/drivers/thermal/tegra/soctherm.h
>> @@ -108,5 +108,9 @@ int tegra_soctherm_calculate_tsensor_calibration(
>> extern struct tegra_soctherm_soc tegra124_soctherm;
>> #endif
>>
>> +#ifdef CONFIG_ARCH_TEGRA_210_SOC
>> +extern struct tegra_soctherm_soc tegra210_soctherm;
>
> I would've expected this to be "const".
Yes, will change it.
>
>> diff --git a/drivers/thermal/tegra/tegra210-soctherm.c b/drivers/thermal/tegra/tegra210-soctherm.c
> [...]
>> +static const struct tegra_tsensor_group tegra210_tsensor_group_cpu = {
>> + .id = TEGRA124_SOCTHERM_SENSOR_CPU,
>> + .name = "cpu",
>> + .sensor_temp_offset = SENSOR_TEMP1,
>> + .sensor_temp_mask = SENSOR_TEMP1_CPU_TEMP_MASK,
>> + .pdiv = 8,
>> + .pdiv_ate = 8,
>> + .pdiv_mask = SENSOR_PDIV_CPU_MASK,
>> + .pllx_hotspot_diff = 10,
>> + .pllx_hotspot_mask = SENSOR_HOTSPOT_CPU_MASK,
>> +};
>
> I prefer single spaces for padding because I find it easier to read that
> way. Also using tabs to make this look like a table has the drawback
> that you run the risk of having to adjust padding for all fields when a
> new field is added whose name is longer than any existing ones. Or you
> have to rely on excessive padding (such as in this case) to make that
> unlikely. So I don't see any advantage in this, but I don't have very
> strong objections either.
Ok, will change it.
>
>> +static const struct tegra_tsensor_group *
>> +tegra210_tsensor_groups[] = {
>
> Why wrap these two lines? They seem to fit on one line and within 78
> columns.
Hmm, will fix it.
>
>> +static struct tegra_tsensor tegra210_tsensors[] = {
>
> "static const"?
Will change to "const".
>
>> + {
>> + .name = "cpu0",
>> + .base = 0xc0,
>> + .config = &tegra210_tsensor_config,
>> + .calib_fuse_offset = 0x098,
>> + .fuse_corr_alpha = 1085000,
>> + .fuse_corr_beta = 3244200,
>> + .group = &tegra210_tsensor_group_cpu,
>> + },
>> + {
>
> "}," and "{" can go on the same line.
Will change it.
>
>> +struct tegra_soctherm_soc tegra210_soctherm = {
>
> "const"?
>
> Thierry
>
> * Unknown Key
> * 0x7F3EB3A1
>
prev parent reply other threads:[~2016-01-25 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 10:03 [PATCH V3 05/11] thermal: tegra: add T210-specific SOC_THERM driver Wei Ni
2016-01-21 14:25 ` Thierry Reding
2016-01-25 5:48 ` Wei Ni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56A5B73B.6040706@nvidia.com \
--to=wni@nvidia.com \
--cc=MLongnecker@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mikko.perttunen@kapsi.fi \
--cc=rui.zhang@intel.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).