R0dn3yS/android_kernel_xiaomi_sm7250
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

BACKPORT: devfreq: Fix suspend callback for non-zero min_freq

Browse Source 
With commit commit 921884ca1498 ("devfreq: Fix PM
callbacks to support zero frequency"), suspend_freq
of zero is considered valid.

However, the devfreq_set_target is called with zero frequency.
To avoid this, do not call devfreq_set_target if the
suspend_freq is less than the minimun allowed frequency.

Change-Id: I506165d28395eb67138ae2dac53e842357809bbb
Signed-off-by: Shreyas K K <shrekk@codeaurora.org>
Signed-off-by: UtsavBalar1231 <utsavbalar1231@gmail.com>
This commit is contained in:
Shreyas K K 2021-11-26 00:35:03 +05:30 committed by spakkkk
parent edfc9ad0c3
commit 89bd841849
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
drivers/devfreq/devfreq.c
View File

@ -321,7 +321,7 @@ static int devfreq_set_target(struct devfreq *devfreq, unsigned long new_freq,
devfreq->previous_freq = new_freq;
if (devfreq->suspend_freq >= 0)
if (devfreq->suspend_freq >= devfreq->scaling_min_freq)
devfreq->resume_freq = cur_freq;
return err;
@ -910,7 +910,7 @@ int devfreq_suspend_device(struct devfreq *devfreq)
return ret;
}
if (devfreq->suspend_freq >= 0) {
if (devfreq->suspend_freq >= devfreq->scaling_min_freq) {
mutex_lock(&devfreq->lock);
ret = devfreq_set_target(devfreq, devfreq->suspend_freq, 0);
mutex_unlock(&devfreq->lock);