linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Eduardo Valentin <eduardo.valentin@ti.com>
Cc: linux-pm@vger.kernel.org, durgadoss.r@intel.com,
	shawn.guo@linaro.org, ruslan.ruslichenko@ti.com
Subject: Re: [RFC PATCH 6/6] Thermal: step_wise: set next cooling target explicitly
Date: Mon, 08 Jul 2013 10:34:53 +0800	[thread overview]
Message-ID: <1373250893.2038.17.camel@rzhang1-mobl4> (raw)
In-Reply-To: <51D34035.3000008@ti.com>

On Tue, 2013-07-02 at 17:03 -0400, Eduardo Valentin wrote:
> On 17-06-2013 09:24, Zhang Rui wrote:
> > Set the next target state explicitly for each thermal trend,
> > in step_wise governor, to provide more readability, and to
> > follow the cooling algorithm description strictly.
> 
> 
> How about merging this one with patch 05?
> 
> > 
> > Signed-off-by: Zhang Rui <rui.zhang@intel.com>
> > ---
> >  drivers/thermal/step_wise.c |    9 +++++++--
> >  1 file changed, 7 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/thermal/step_wise.c b/drivers/thermal/step_wise.c
> > index 53b56e6..ffa553f 100644
> > --- a/drivers/thermal/step_wise.c
> > +++ b/drivers/thermal/step_wise.c
> > @@ -60,7 +60,6 @@ static unsigned long get_target_state(struct thermal_instance *instance,
> >  	 * cdev in use to determine the next_target.
> >  	 */
> >  	cdev->ops->get_cur_state(cdev, &cur_state);
> > -	next_target = instance->target;
> >  
> >  	switch (trend) {
> >  	case THERMAL_TREND_RAISING:
> > @@ -69,11 +68,14 @@ static unsigned long get_target_state(struct thermal_instance *instance,
> >  				    (cur_state + 1) : instance->upper;
> >  			if (next_target < instance->lower)
> >  				next_target = instance->lower;
> > -		}
> > +		} else
> > +			next_target = instance->target;
> >  		break;
> >  	case THERMAL_TREND_RAISE_FULL:
> >  		if (throttle)
> >  			next_target = instance->upper;
> > +		else
> > +			next_target = instance->target;
> >  		break;
> >  	case THERMAL_TREND_DROPPING:
> >  		if (throttle) {
> > @@ -99,7 +101,10 @@ static unsigned long get_target_state(struct thermal_instance *instance,
> >  		break;
> >  	case THERMAL_TREND_STABLE:
> >  		/* Do nothing */
> > +		next_target = instance->target;
> > +		break;
> >  	default:
> > +		next_target = instance->target;
> >  		break;
> 
> 
> The above could be rewritten like this:
>   	case THERMAL_TREND_STABLE:
>   		/* Do nothing */
>   	default:
>  		next_target = instance->target;
>   		break;
> 

sure I'm okay with your suggestion.
I wrote the code in this way because I want to keep the code follows the
description explicitly.

thanks,
rui
> >  	}
> >  
> > 
> 
> 



  reply	other threads:[~2013-07-08  2:34 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
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 [this message]
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=1373250893.2038.17.camel@rzhang1-mobl4 \
    --to=rui.zhang@intel.com \
    --cc=durgadoss.r@intel.com \
    --cc=eduardo.valentin@ti.com \
    --cc=linux-pm@vger.kernel.org \
    --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 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).