From: Javi Merino <javi.merino@arm.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH V4 1/3] Thermal: initialize thermal zone device correctly
Date: Thu, 9 Apr 2015 15:56:44 +0100 [thread overview]
Message-ID: <20150409145644.GB27702@e104805> (raw)
In-Reply-To: <1428373476-14257-2-git-send-email-rui.zhang@intel.com>
On Tue, Apr 07, 2015 at 03:24:34AM +0100, Zhang Rui wrote:
> After thermal zone device registered, as we have not read any
> temperature before, thus tz->temperature should not be 0, which actually
> means 0C, and thermal trend is not available.
> In this case, we need specially handling for the first
> thermal_zone_device_update().
>
> Both thermal core framework and step_wise governor is enhanced to handle this.
>
> CC: <stable@vger.kernel.org> #3.18+
> Tested-by: Manuel Krause <manuelkrause@netscape.net>
> Tested-by: szegad <szegadlo@poczta.onet.pl>
> Tested-by: prash <prash.n.rao@gmail.com>
> Tested-by: amish <ammdispose-arch@yahoo.com>
> Tested-by: Matthias <morpheusxyz123@yahoo.de>
> Signed-off-by: Zhang Rui <rui.zhang@intel.com>
> ---
> drivers/thermal/step_wise.c | 15 +++++++++++++--
> drivers/thermal/thermal_core.c | 19 +++++++++++++++++--
> drivers/thermal/thermal_core.h | 1 +
> include/linux/thermal.h | 3 +++
> 4 files changed, 34 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/thermal/step_wise.c b/drivers/thermal/step_wise.c
> index 5a0f12d..c2bb37c 100644
> --- a/drivers/thermal/step_wise.c
> +++ b/drivers/thermal/step_wise.c
> @@ -63,6 +63,16 @@ static unsigned long get_target_state(struct thermal_instance *instance,
> next_target = instance->target;
> dev_dbg(&cdev->device, "cur_state=%ld\n", cur_state);
>
> + if (!instance->initialized) {
> + if (throttle) {
> + next_target = (cur_state + 1) >= instance->upper ?
> + instance->upper :
> + ((cur_state + 1) < instance->lower ?
> + instance->lower : (cur_state + 1));
> + } else
> + next_target = THERMAL_NO_TARGET;
CodingStyle says that if one branch of an if statement needs braces,
all branches must have braces:
if (condition) {
do_this();
do_that();
} else {
otherwise();
}
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/CodingStyle#n169
> + }
> +
I pointed out before and I think Eduardo has said it as well. I think
you should "return next_target;" at the end of the "if
(!instance->initialized)"
> switch (trend) {
> case THERMAL_TREND_RAISING:
> if (throttle) {
Cheers,
Javi
next prev parent reply other threads:[~2015-04-09 14:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 2:24 [PATCH V4 0/3] Thermal: thermal enhancements for boot and system sleep Zhang Rui
2015-04-07 2:24 ` [PATCH V4 1/3] Thermal: initialize thermal zone device correctly Zhang Rui
2015-04-07 2:47 ` Eduardo Valentin
2015-04-08 13:01 ` Zhang, Rui
2015-04-08 15:03 ` Eduardo Valentin
2015-04-09 15:26 ` Zhang, Rui
2015-04-09 14:44 ` Javi Merino
2015-04-09 15:45 ` Zhang, Rui
2015-04-09 14:56 ` Javi Merino [this message]
2015-04-09 15:37 ` Zhang, Rui
2015-04-07 2:24 ` [PATCH V4 2/3] Thermal: handle thermal zone device properly during system sleep Zhang Rui
2015-04-07 2:24 ` [PATCH V4 3/3] Thermal: do thermal zone update after a cooling device registered Zhang Rui
2015-04-08 15:04 ` Eduardo Valentin
2015-04-09 15:14 ` 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=20150409145644.GB27702@e104805 \
--to=javi.merino@arm.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