From: Eduardo Valentin <edubezval@gmail.com>
To: Michael Tatarinov <kukabu@gmail.com>
Cc: linux-pm@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH] of: thermal: Introduce "hwmon" optional property
Date: Mon, 4 Dec 2017 17:46:17 -0800 [thread overview]
Message-ID: <20171205014615.GA3536@localhost.localdomain> (raw)
In-Reply-To: <CABrG=Zy7SYZBP6PyZ4aP6Fi5q3k5nCh6b5shN=CtOYTQ2DDoTA@mail.gmail.com>
On Wed, Jul 12, 2017 at 11:49:10AM +0400, Michael Tatarinov wrote:
> Hello
>
> Some clarifications for this patch.
> I uses CONFIG_THERMAL_HWMON feature on Raspberry PI. It works ok with
> the downstream thermal driver because it uses
> thermal_zone_device_register(). After I switches to the upstream
> driver this feature doesn't work because it uses
> thermal_zone_of_sensor_register().
> I would like to use this opportunity and in the future.
I would be OK with the linux,no-hwmon flag, but that needs to be acked
by the DT folks.
>
> 2017-07-10 15:51 GMT+04:00, Michael Tatarinov <kukabu@gmail.com>:
> > Introduce an optional property called, hwmon, which enable
> > registration in hwmon subsystems.
> >
> > Cc: Zhang Rui <rui.zhang@intel.com>
> > Cc: Eduardo Valentin <edubezval@gmail.com>
> > Signed-off-by: Michael Tatarinov <kukabu@gmail.com>
> > ---
> > Documentation/devicetree/bindings/thermal/thermal.txt | 6 ++++++
> > drivers/thermal/of-thermal.c | 3 +--
> > 2 files changed, 7 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/thermal/thermal.txt
> > b/Documentation/devicetree/bindings/thermal/thermal.txt
> > index 88b6ea1ad290..4e51fbd4efa2 100644
> > --- a/Documentation/devicetree/bindings/thermal/thermal.txt
> > +++ b/Documentation/devicetree/bindings/thermal/thermal.txt
> > @@ -175,6 +175,10 @@ Optional property:
> > 2000mW, while on a 10'' tablet is around
> > 4500mW.
> >
> > +- hwmon: Register the thermal zone in hwmon subsystems
> > + Type: boolean (requires CONFIG_THERMAL_HWMON).
> > + Size: one cell
> > +
> > Note: The delay properties are bound to the maximum dT/dt (temperature
> > derivative over time) in two situations for a thermal zone:
> > (i) - when passive cooling is activated (polling-delay-passive); and
> > @@ -556,6 +560,8 @@ thermal-zones {
> >
> > sustainable-power = <2500>;
> >
> > + hwmon;
> > +
> > trips {
> > /* Trips are based on resulting linear equation */
> > cpu_trip: cpu-trip {
> > diff --git a/drivers/thermal/of-thermal.c b/drivers/thermal/of-thermal.c
> > index d04ec3b9e5ff..ce580a57313b 100644
> > --- a/drivers/thermal/of-thermal.c
> > +++ b/drivers/thermal/of-thermal.c
> > @@ -994,8 +994,7 @@ int __init of_parse_thermal_zones(void)
> > goto exit_free;
> > }
> >
> > - /* No hwmon because there might be hwmon drivers registering */
> > - tzp->no_hwmon = true;
> > + tzp->no_hwmon = !of_property_read_bool(child, "hwmon");
> >
> > if (!of_property_read_u32(child, "sustainable-power", &prop))
> > tzp->sustainable_power = prop;
> > --
> > 2.9.4
> >
> >
next prev parent reply other threads:[~2017-12-05 1:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 11:51 [PATCH] of: thermal: Introduce "hwmon" optional property Michael Tatarinov
2017-07-12 7:49 ` Michael Tatarinov
2017-12-05 1:46 ` Eduardo Valentin [this message]
2017-08-31 15:08 ` Guenter Roeck
2017-09-02 5:53 ` Michael Tatarinov
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=20171205014615.GA3536@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=kukabu@gmail.com \
--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 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).