From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
Cc: rui.zhang@intel.com, jason@lakedaemon.net,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 1/2] thermal: Add support for thermal sensor for Kirkwood SoC
Date: Sat, 8 Dec 2012 01:07:08 +0100 [thread overview]
Message-ID: <20121208010708.260209f5@skate> (raw)
In-Reply-To: <1354922151-3250-1-git-send-email-iwamatsu@nigauri.org>
Hello,
On Sat, 8 Dec 2012 08:15:50 +0900, Nobuhiro Iwamatsu wrote:
> +config KIRKWOOD_THERMAL
> + tristate "Temperature sensor on Marvel Kirkwood"
Marvell
> + /* Valid check */
> + if (!(reg >> THERMAL_VALID_OFFSET) & THERMAL_VALID_MASK) {
> + dev_info(&thermal->device, "Reading temperature is not valid\n");
"Temperature read is not valid" maybe? An native english speaker could
say.
> + thermal_dev
> + = devm_kzalloc(&pdev->dev, sizeof(*thermal_dev), GFP_KERNEL);
I think the usual coding style is to have the = on the first line.
> +static int kirkwood_thermal_exit(struct platform_device *pdev)
> +{
> + struct thermal_zone_device *kirkwood_thermal
> + = platform_get_drvdata(pdev);
Ditto.
> +static const struct of_device_id kirkwood_thermal_id_table[] = {
> + { .compatible = "marvel,thermal-kirkwood" },
marvel -> marvell
Also, I think it should be marvell,kirkwood-thermal, since most other
DT compatible strings that we have for Marvell SoCs are
marvell,<soc>-<function>.
Also, the Device Tree binding documentation is missing (even though it
is admittedly going to be a very short documentation).
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] thermal: Add support for thermal sensor for Kirkwood SoC
Date: Sat, 8 Dec 2012 01:07:08 +0100 [thread overview]
Message-ID: <20121208010708.260209f5@skate> (raw)
In-Reply-To: <1354922151-3250-1-git-send-email-iwamatsu@nigauri.org>
Hello,
On Sat, 8 Dec 2012 08:15:50 +0900, Nobuhiro Iwamatsu wrote:
> +config KIRKWOOD_THERMAL
> + tristate "Temperature sensor on Marvel Kirkwood"
Marvell
> + /* Valid check */
> + if (!(reg >> THERMAL_VALID_OFFSET) & THERMAL_VALID_MASK) {
> + dev_info(&thermal->device, "Reading temperature is not valid\n");
"Temperature read is not valid" maybe? An native english speaker could
say.
> + thermal_dev
> + = devm_kzalloc(&pdev->dev, sizeof(*thermal_dev), GFP_KERNEL);
I think the usual coding style is to have the = on the first line.
> +static int kirkwood_thermal_exit(struct platform_device *pdev)
> +{
> + struct thermal_zone_device *kirkwood_thermal
> + = platform_get_drvdata(pdev);
Ditto.
> +static const struct of_device_id kirkwood_thermal_id_table[] = {
> + { .compatible = "marvel,thermal-kirkwood" },
marvel -> marvell
Also, I think it should be marvell,kirkwood-thermal, since most other
DT compatible strings that we have for Marvell SoCs are
marvell,<soc>-<function>.
Also, the Device Tree binding documentation is missing (even though it
is admittedly going to be a very short documentation).
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-12-08 0:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 23:15 [PATCH 1/2] thermal: Add support for thermal sensor for Kirkwood SoC Nobuhiro Iwamatsu
2012-12-07 23:15 ` Nobuhiro Iwamatsu
2012-12-07 23:15 ` [PATCH 2/2] ARM: Kirkwood: Add support thermal sensor for 88F6282 and 88F6283 Nobuhiro Iwamatsu
2012-12-07 23:15 ` Nobuhiro Iwamatsu
2012-12-07 23:24 ` [PATCH 1/2] thermal: Add support for thermal sensor for Kirkwood SoC Jason Gunthorpe
2012-12-07 23:24 ` Jason Gunthorpe
2012-12-07 23:59 ` Jason Gunthorpe
2012-12-07 23:59 ` Jason Gunthorpe
2012-12-08 0:08 ` Russell King - ARM Linux
2012-12-08 0:08 ` Russell King - ARM Linux
2012-12-14 21:25 ` Nobuhiro Iwamatsu
2012-12-14 21:25 ` Nobuhiro Iwamatsu
2012-12-14 21:22 ` Nobuhiro Iwamatsu
2012-12-14 21:22 ` Nobuhiro Iwamatsu
2012-12-08 0:07 ` Thomas Petazzoni [this message]
2012-12-08 0:07 ` Thomas Petazzoni
2012-12-08 0:11 ` Russell King - ARM Linux
2012-12-08 0:11 ` Russell King - ARM Linux
2012-12-09 13:54 ` Sebastian Hesselbarth
2012-12-09 13:54 ` Sebastian Hesselbarth
2012-12-14 21:31 ` Nobuhiro Iwamatsu
2012-12-14 21:31 ` Nobuhiro Iwamatsu
2012-12-14 21:24 ` Nobuhiro Iwamatsu
2012-12-14 21:24 ` Nobuhiro Iwamatsu
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=20121208010708.260209f5@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=iwamatsu@nigauri.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.