From: Guenter Roeck <linux@roeck-us.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Jean Delvare <jdelvare@suse.com>, Wei Ni <wni@nvidia.com>
Subject: Re: [RFC 2/2] hwmon: lm90: add thermal_zone temperature sensor support
Date: Mon, 6 Feb 2017 11:37:20 -0800 [thread overview]
Message-ID: <20170206193720.GA24834@roeck-us.net> (raw)
In-Reply-To: <6489282.5YPtSL3FNJ@debian64>
On Mon, Feb 06, 2017 at 05:01:31PM +0100, Christian Lamparter wrote:
> On Sunday, February 5, 2017 7:10:53 PM CET Guenter Roeck wrote:
> > On 02/05/2017 01:03 PM, Christian Lamparter wrote:
> > > This patch adds thermal_zone temperature sensor support
> > > to the lm90 module. The feature has to be enabled
> > > separately via the Kconfig option:
> > > CONFIG_SENSORS_LM90_THERMAL_DEVICE
> > >
> > > The LM90 supports two (three for MAX6695 and MAX6696)
> > > temperature sensors. The local sensor is integrated
> > > into the LM90 chip. The remote sensors are connected
> > > to external temperature sensing diodes.
> > >
> > > Cc: Wei Ni <wni@nvidia.com>
> > > Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
> >
> > Since the hwnmon core now supports thermal registration, and since the lm90
> > driver has already been converted to using the new hwmon API, I would
> > rather like to understand why using the hwmon core for this purpose is
> > insufficient, and I would prefer to address the deficiencies in the hwmon
> > core and not in the driver.
>
> Hey, that's great, I completely missed that! Yes, this makes the changes
> to lm90.c obsolete.
>
> However, what about the device-tree updates in 1/2? I'm asking because
> the hwmon device node still needs the #thermal-sensor-cells property
> defined for thermal_zone_of_sensor_register(). Without it, the sensor
> will be skipped and the thermal-zones will do nothing (no regulation).
> I can respin the device-tree patch (local and remote need to trade
> places). What do you think?
>
Sure, no problem with that. Does supporting this require changes in the hwmon
core ?
Thanks,
Guenter
next prev parent reply other threads:[~2017-02-06 19:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 21:03 [RFC 1/2] devicetree: add lm90 thermal_zone sensor support Christian Lamparter
2017-02-05 21:03 ` [RFC 2/2] hwmon: lm90: add thermal_zone temperature " Christian Lamparter
2017-02-06 3:10 ` Guenter Roeck
[not found] ` <edca1928-6909-f353-3524-30546d715ed3-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2017-02-06 16:01 ` Christian Lamparter
2017-02-06 19:37 ` Guenter Roeck [this message]
2017-02-08 22:30 ` [RFC 1/2] devicetree: add lm90 thermal_zone " Rob Herring
2017-02-08 23:01 ` Christian Lamparter
2017-02-10 16:12 ` [PATCH " Christian Lamparter
2017-02-10 23:51 ` Guenter Roeck
[not found] ` <0d274e32ad09daa2f6f7f27f1c36d39da526b66d.1486741517.git.chunkeey-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-02-10 16:12 ` [PATCH 2/2] hwmon: lm90: integration of channel map in dt-bindings Christian Lamparter
2017-02-10 17:21 ` Guenter Roeck
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=20170206193720.GA24834@roeck-us.net \
--to=linux@roeck-us.net \
--cc=chunkeey@googlemail.com \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wni@nvidia.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).