From: Javi Merino <javi.merino@arm.com>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Punit Agrawal <Punit.Agrawal@arm.com>,
"broonie@kernel.org" <broonie@kernel.org>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: [RFC PATCH v6 9/9] of: thermal: Introduce sustainable power for a thermal zone
Date: Tue, 6 Jan 2015 13:29:21 +0000 [thread overview]
Message-ID: <20150106132921.GG2885@e104805> (raw)
In-Reply-To: <20150106131301.GC4661@developer>
On Tue, Jan 06, 2015 at 01:13:03PM +0000, Eduardo Valentin wrote:
> On Tue, Jan 06, 2015 at 09:42:15AM +0000, Javi Merino wrote:
> > On Fri, Jan 02, 2015 at 03:53:00PM +0000, Eduardo Valentin wrote:
> > > On Fri, Dec 05, 2014 at 07:04:20PM +0000, Javi Merino wrote:
> > > > From: Punit Agrawal <punit.agrawal@arm.com>
> > > >
> > > > Introduce an optional property called, sustainable-power, which
> > > > represents the power (in mW) which the thermal zone can safely
> > > > dissipate.
> > > >
> > > > If provided the property is parsed and associated with the thermal
> > > > zone via the thermal zone parameters.
> > > >
> > > > Cc: Zhang Rui <rui.zhang@intel.com>
> > > > Cc: Eduardo Valentin <edubezval@gmail.com>
> > > > Signed-off-by: Punit Agrawal <punit.agrawal@arm.com>
> > > > ---
> > > > Documentation/devicetree/bindings/thermal/thermal.txt | 4 ++++
> > > > drivers/thermal/of-thermal.c | 4 ++++
> > > > 2 files changed, 8 insertions(+)
> > > >
> > > > diff --git a/Documentation/devicetree/bindings/thermal/thermal.txt b/Documentation/devicetree/bindings/thermal/thermal.txt
> > > > index f5db6b72a36f..c6eb9a8d2aed 100644
> > > > --- a/Documentation/devicetree/bindings/thermal/thermal.txt
> > > > +++ b/Documentation/devicetree/bindings/thermal/thermal.txt
> > > > @@ -167,6 +167,10 @@ Optional property:
> > > > by means of sensor ID. Additional coefficients are
> > > > interpreted as constant offset.
> > > >
> > > > +- sustainable-power: An estimate of the sustainable power (in mW) that the
> > > > + Type: unsigned thermal zone can dissipate.
> > > > + Size: one cell
> > > > +
> > >
> > > Please, include examples of this property, as you mentioned in the
> > > governor documentation.
> >
> > I'd rather put a pointer to the documentation instead of repeating the
> > same thing here. What do you think?
>
> The point is that device tree and Linux are supposed to be independent
> entities. I would prefer if you could extend the explanation of what is
> 'sustainable power' in the above entry. On top of that, pick one of the
> existing examples and extend it to include the 'sustainable-power' property,
> with a comment explaining it, for instance.
Ok, I'll do that.
Cheers,
Javi
prev parent reply other threads:[~2015-01-06 13:29 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 19:04 [RFC PATCH v6 0/9] The power allocator thermal governor Javi Merino
2014-12-05 19:04 ` [RFC PATCH v6 1/9] tracing: Add array printing helpers Javi Merino
2014-12-08 14:39 ` Dave P Martin
2014-12-08 15:42 ` Steven Rostedt
2014-12-08 16:04 ` Dave P Martin
2014-12-10 10:52 ` Javi Merino
2014-12-05 19:04 ` [RFC PATCH v6 2/9] tools lib traceevent: Generalize numeric argument Javi Merino
2014-12-05 19:04 ` [RFC PATCH v6 3/9] tools lib traceevent: Add support for __print_u{8,16,32,64}_array() Javi Merino
2014-12-05 19:04 ` [RFC PATCH v6 4/9] thermal: let governors have private data for each thermal zone Javi Merino
2014-12-08 4:11 ` Zhang Rui
2015-01-23 14:33 ` Javi Merino
2014-12-05 19:04 ` [RFC PATCH v6 5/9] thermal: extend the cooling device API to include power information Javi Merino
2014-12-23 15:14 ` Eduardo Valentin
2015-01-05 15:37 ` Javi Merino
2015-01-05 21:04 ` Eduardo Valentin
2015-01-06 10:34 ` Javi Merino
2015-01-06 13:08 ` Eduardo Valentin
2014-12-05 19:04 ` [RFC PATCH v6 6/9] thermal: cpu_cooling: implement the power cooling device API Javi Merino
2014-12-08 5:49 ` Viresh Kumar
2014-12-08 12:50 ` Javi Merino
2014-12-08 13:31 ` Viresh Kumar
2014-12-08 14:22 ` Javi Merino
2014-12-09 1:59 ` Viresh Kumar
2014-12-09 10:32 ` Javi Merino
2014-12-09 10:36 ` Viresh Kumar
2014-12-09 11:00 ` Javi Merino
2014-12-09 11:06 ` Viresh Kumar
2014-12-09 11:23 ` Javi Merino
2015-01-02 14:37 ` Eduardo Valentin
2015-01-05 16:53 ` Javi Merino
2015-01-05 20:44 ` Eduardo Valentin
2015-01-06 11:01 ` Javi Merino
2015-01-28 5:23 ` Eduardo Valentin
2015-01-29 11:19 ` Punit Agrawal
2015-01-29 0:15 ` Eduardo Valentin
2015-01-29 19:06 ` Javi Merino
2014-12-05 19:04 ` [RFC PATCH v6 7/9] thermal: introduce the Power Allocator governor Javi Merino
2015-01-02 15:46 ` Eduardo Valentin
2015-01-06 13:23 ` Javi Merino
2015-01-06 14:18 ` Eduardo Valentin
2015-01-06 14:50 ` Javi Merino
2015-01-02 15:51 ` Eduardo Valentin
2014-12-05 19:04 ` [RFC PATCH v6 8/9] thermal: add trace events to the power allocator governor Javi Merino
2014-12-05 19:04 ` [RFC PATCH v6 9/9] of: thermal: Introduce sustainable power for a thermal zone Javi Merino
2015-01-02 15:53 ` Eduardo Valentin
2015-01-06 9:42 ` Javi Merino
2015-01-06 13:13 ` Eduardo Valentin
2015-01-06 13:29 ` Javi Merino [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=20150106132921.GG2885@e104805 \
--to=javi.merino@arm.com \
--cc=Punit.Agrawal@arm.com \
--cc=broonie@kernel.org \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.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 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).