From: Eduardo Valentin <eduardo.valentin@ti.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-pm@vger.kernel.org, eduardo.valentin@ti.com,
durgadoss.r@intel.com, shawn.guo@linaro.org,
ruslan.ruslichenko@ti.com
Subject: Re: [RFC PATCH 4/6] Thermal: fix step_wise handling of THERMAL_TREND_DROP_EFULL
Date: Tue, 2 Jul 2013 17:11:17 -0400 [thread overview]
Message-ID: <51D341F5.8080905@ti.com> (raw)
In-Reply-To: <1371475468-5351-5-git-send-email-rui.zhang@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]
On subject s/THERMAL_TREND_DROP_EFULL/THERMAL_TREND_DROP_FULL/g
On 17-06-2013 09:24, Zhang Rui wrote:
> Change the step_wise cooling algorithm to handle
> THERMAL_TREND_DROP_FULL a bit differently.
>
> When the temperature is higher than the trip point,
> we should always use the instance->lower as the next target state.
> When the temperature is lower than the trip point,
> we should always deactive the thermal instance.
s/deactive/deactivate/g
Are you expecting to optimize the system in which way by doing this
change? In which situation we would need to set to instance->lower if we
are at a state which trend is dropping fully?
>
> Signed-off-by: Zhang Rui <rui.zhang@intel.com>
> ---
> drivers/thermal/step_wise.c | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/thermal/step_wise.c b/drivers/thermal/step_wise.c
> index f0cc5e5..84d6e90 100644
> --- a/drivers/thermal/step_wise.c
> +++ b/drivers/thermal/step_wise.c
> @@ -42,9 +42,8 @@
> * state for this trip point, if the cooling state already
> * equals lower limit, deactivate the thermal instance
> * c. if the trend is THERMAL_TREND_RAISE_FULL, do nothing
> - * d. if the trend is THERMAL_TREND_DROP_FULL, use lower limit,
> - * if the cooling state already equals lower limit,
> - * deactive the thermal instance
> + * d. if the trend is THERMAL_TREND_DROP_FULL, deactive
> + * the thermal instance
> */
> static unsigned long get_target_state(struct thermal_instance *instance,
> enum thermal_trend trend, bool throttle)
> @@ -91,11 +90,10 @@ static unsigned long get_target_state(struct thermal_instance *instance,
> }
> break;
> case THERMAL_TREND_DROP_FULL:
> - if (cur_state == instance->lower) {
> - if (!throttle)
> - next_target = THERMAL_NO_TARGET;
> - } else
> + if (throttle)
> next_target = instance->lower;
> + else
> + next_target = THERMAL_NO_TARGET;
> break;
> default:
> break;
>
--
You have got to be excited about what you are doing. (L. Lamport)
Eduardo Valentin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 295 bytes --]
next prev parent reply other threads:[~2013-07-02 21:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 13:24 [RFC PATCH 0/6] Thermal: step_wise governor fixes Zhang Rui
2013-06-17 13:24 ` [RFC PATCH 1/6] thermal: step_wise: cdev only needs update on a new target state Zhang Rui
2013-06-17 13:24 ` [RFC PATCH 2/6] thermal: step_wise: return instance->target by default Zhang Rui
2013-06-17 13:24 ` [RFC PATCH 3/6] Thermal: fix step_wise handling of THERMAL_TREND_DROPPING Zhang Rui
2013-07-02 20:57 ` Eduardo Valentin
2013-07-08 2:32 ` Zhang Rui
2013-06-17 13:24 ` [RFC PATCH 4/6] Thermal: fix step_wise handling of THERMAL_TREND_DROP_EFULL Zhang Rui
2013-07-02 21:11 ` Eduardo Valentin [this message]
2013-07-08 2:35 ` Zhang Rui
2013-06-17 13:24 ` [RFC PATCH 5/6] Thermal: step_wise handle THERMAL_TREND_STABLE explicitly Zhang Rui
2013-06-17 13:24 ` [RFC PATCH 6/6] Thermal: step_wise: set next cooling target explicitly Zhang Rui
2013-07-02 21:03 ` Eduardo Valentin
2013-07-08 2:34 ` Zhang Rui
2013-07-02 21:05 ` Eduardo Valentin
2013-06-18 3:45 ` [RFC PATCH 0/6] Thermal: step_wise governor fixes Shawn Guo
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=51D341F5.8080905@ti.com \
--to=eduardo.valentin@ti.com \
--cc=durgadoss.r@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=ruslan.ruslichenko@ti.com \
--cc=shawn.guo@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.