From: Javi Merino <javi.merino@arm.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
eduardo <eduardo.valentin@ti.com>,
"wni@nvidia.com" <wni@nvidia.com>
Subject: Re: [PATCH] Thermal: thermal zone governor fix
Date: Mon, 3 Mar 2014 10:00:37 +0000 [thread overview]
Message-ID: <20140303100035.GA3576@e102654-lin.cambridge.arm.com> (raw)
In-Reply-To: <1393825573.2199.3.camel@rzhang1-mobl4>
Hi Rui,
On Mon, Mar 03, 2014 at 05:46:13AM +0000, Zhang Rui wrote:
> From 635a1f41a8f95a35d1bf24c9cc018ffb018a93e6 Mon Sep 17 00:00:00 2001
> From: Zhang Rui <rui.zhang@intel.com>
> Date: Fri, 24 Jan 2014 10:23:19 +0800
> Subject: [PATCH] Thermal: thermal zone governor fix
>
> This patch does a cleanup about the thermal zone govenor,
> setting and make the following rule.
> 1. For thermal zone devices that are registered w/o tz->tzp,
> they can use the default thermal governor only.
> 2. For thermal zone devices w/ governor name specified in
> tz->tzp->governor_name, we will use the default govenor
> if the governor specified is not available at the moment,
> and update tz->governor when the matched governor is registered.
>
> Signed-off-by: Zhang Rui <rui.zhang@intel.com>
This solves my issue. You can add my Acked-by.
I was a bit worried about dereferencing def_governor in
handle_non_critical_trips() without checking if it's initialised. I
guess that all the thermal zones initialise in device_initcall or
later so by the time they run thermal_zone_device_update(),
thermal_register_governors() must have initialised the default
governor. So it's not an issue.
Thanks,
Javi
next prev parent reply other threads:[~2014-03-03 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 5:46 [PATCH] Thermal: thermal zone governor fix Zhang Rui
2014-03-03 10:00 ` Javi Merino [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-27 6:41 Zhang Rui
2014-02-27 6:47 ` Zhang Rui
2014-02-27 13:41 ` Javi Merino
2014-02-27 14:21 ` Zhang, Rui
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=20140303100035.GA3576@e102654-lin.cambridge.arm.com \
--to=javi.merino@arm.com \
--cc=eduardo.valentin@ti.com \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--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