From: Zhang Rui <rui.zhang@intel.com>
To: Linux PM list <linux-pm@vger.kernel.org>
Cc: "Zhang, Rui" <rui.zhang@intel.com>,
Amit Kachhap <amit.kachhap@linaro.org>,
durga <durgadoss.r@intel.com>
Subject: [PATCH 2/2] Thermal: Introduce THERMAL_TREND_RAISE/DROP_FULL support for step_wise governor
Date: Mon, 19 Nov 2012 16:21:33 +0800 [thread overview]
Message-ID: <1353313293.6468.4.camel@rzhang1-mobl4> (raw)
>From fcc7e0a36388f468c25526290e2fb2beebaae99c Mon Sep 17 00:00:00 2001
From: Zhang Rui <rui.zhang@intel.com>
Date: Mon, 19 Nov 2012 16:10:20 +0800
Subject: [PATCH 2/2] Introduce THERMAL_TREND_RAISE/DROP_FULL support for
step_wise governor
step_wise governor should set the device cooling state to
upper/lower limit directly when THERMAL_TREND_RAISE/DROP_FULL.
Signed-off-by: Zhang Rui <rui.zhang@intel.com>
---
drivers/thermal/step_wise.c | 19 +++++++++++++++++--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/drivers/thermal/step_wise.c b/drivers/thermal/step_wise.c
index 1242cff..6273f7d 100644
--- a/drivers/thermal/step_wise.c
+++ b/drivers/thermal/step_wise.c
@@ -35,6 +35,10 @@
* state for this trip point
* b. if the trend is THERMAL_TREND_DROPPING, use lower cooling
* state for this trip point
+ * c. if the trend is THERMAL_TREND_RAISE_FULL, use upper limit
+ * for this trip point
+ * d. if the trend is THERMAL_TREND_DROP_FULL, use lower limit
+ * for this trip point
*/
static unsigned long get_target_state(struct thermal_instance *instance,
enum thermal_trend trend)
@@ -44,12 +48,23 @@ static unsigned long get_target_state(struct thermal_instance *instance,
cdev->ops->get_cur_state(cdev, &cur_state);
- if (trend == THERMAL_TREND_RAISING) {
+ switch (trend) {
+ case THERMAL_TREND_RAISING:
cur_state = cur_state < instance->upper ?
(cur_state + 1) : instance->upper;
- } else if (trend == THERMAL_TREND_DROPPING) {
+ break;
+ case THERMAL_TREND_DROPPING:
cur_state = cur_state > instance->lower ?
(cur_state - 1) : instance->lower;
+ break;
+ case THERMAL_TREND_RAISE_FULL:
+ cur_state = instance->upper;
+ break;
+ case THERMAL_TREND_DROP_FULL:
+ cur_state = instance->lower;
+ break;
+ default:
+ break;
}
return cur_state;
--
1.7.9.5
next reply other threads:[~2012-11-19 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 8:21 Zhang Rui [this message]
2012-11-19 11:21 ` [PATCH 2/2] Thermal: Introduce THERMAL_TREND_RAISE/DROP_FULL support for step_wise governor R, Durgadoss
2012-11-21 9:37 ` Amit Kachhap
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=1353313293.6468.4.camel@rzhang1-mobl4 \
--to=rui.zhang@intel.com \
--cc=amit.kachhap@linaro.org \
--cc=durgadoss.r@intel.com \
--cc=linux-pm@vger.kernel.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.