summaryrefslogtreecommitdiff
path: root/drivers/devfreq/governor_powersave.c
diff options
context:
space:
mode:
authorMatthias Kaehlcke <mka@chromium.org>2018-08-03 13:05:10 -0700
committerMyungJoo Ham <myungjoo.ham@samsung.com>2018-10-02 10:16:41 +0900
commit6ff66e2a008337b8a005fd0ae2037bed716262cc (patch)
tree41850ac28462aec890606158d4c371f81f19bdbf /drivers/devfreq/governor_powersave.c
parentdf5cf4a36178c5d4f2b8b9469cb2f722e64cd102 (diff)
PM / devfreq: Don't adjust to user limits in governors
Several governors use the user space limits df->min/max_freq to adjust the target frequency. This is not necessary, since update_devfreq() already takes care of this. Instead the governor can request the available min/max frequency by setting the target frequency to DEVFREQ_MIN/MAX_FREQ and let update_devfreq() take care of any adjustments. Signed-off-by: Matthias Kaehlcke <mka@chromium.org> Reviewed-by: Brian Norris <briannorris@chromium.org> Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com> Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Diffstat (limited to 'drivers/devfreq/governor_powersave.c')
-rw-r--r--drivers/devfreq/governor_powersave.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/devfreq/governor_powersave.c b/drivers/devfreq/governor_powersave.c
index 0c42f23249ef..9e8897f5ac42 100644
--- a/drivers/devfreq/governor_powersave.c
+++ b/drivers/devfreq/governor_powersave.c
@@ -20,7 +20,7 @@ static int devfreq_powersave_func(struct devfreq *df,
* target callback should be able to get ceiling value as
* said in devfreq.h
*/
- *freq = df->min_freq;
+ *freq = DEVFREQ_MIN_FREQ;
return 0;
}