PM / devfreq: Don't adjust to user limits in governors
authorMatthias Kaehlcke <mka@chromium.org>
Fri, 3 Aug 2018 20:05:10 +0000 (13:05 -0700)
committerMyungJoo Ham <myungjoo.ham@samsung.com>
Tue, 2 Oct 2018 01:16:41 +0000 (10:16 +0900)
commit6ff66e2a008337b8a005fd0ae2037bed716262cc
tree41850ac28462aec890606158d4c371f81f19bdbf
parentdf5cf4a36178c5d4f2b8b9469cb2f722e64cd102
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>
drivers/devfreq/governor.h
drivers/devfreq/governor_performance.c
drivers/devfreq/governor_powersave.c
drivers/devfreq/governor_simpleondemand.c
drivers/devfreq/governor_userspace.c