thermal: devfreq_cooling: Use PM QoS to set frequency limits
authorMatthias Kaehlcke <mka@chromium.org>
Wed, 18 Mar 2020 11:45:46 +0000 (11:45 +0000)
committerDaniel Lezcano <daniel.lezcano@linaro.org>
Tue, 14 Apr 2020 09:41:12 +0000 (11:41 +0200)
commit04fa9c804b0ed50a3c6bae1d4b60a2494c81a23f
tree331385d600293a12c5a75c5252570ec5f108efab
parent44fc73223eebaf4a0c970072819d34ff1d92ce7b
thermal: devfreq_cooling: Use PM QoS to set frequency limits

Now that devfreq supports limiting the frequency range of a device
through PM QoS make use of it instead of disabling OPPs that should
not be used.

The switch from disabling OPPs to PM QoS introduces a subtle behavioral
change in case of conflicting requests (min > max): PM QoS gives
precedence to the MIN_FREQUENCY request, while higher OPPs disabled
with dev_pm_opp_disable() would override MIN_FREQUENCY.

Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20200318114548.19916-4-lukasz.luba@arm.com
drivers/thermal/devfreq_cooling.c