Deepak Nibade d63c243547 devfreq: don't set last_scale for same freq ...

In nvhost_pod_estimate_freq(), we have *freq = 0
in case we decide to keep same frequency
In that case we set *freq as current frequency and
then set last_scale timestamp

This can result in keeping same frequency for
long duration due to less delta from last_scale

To fix this, return immediately in case *freq
is zero and do not set last_scale timestamp

Bug 200255163

Change-Id: Ie13bf54e2415c4016a101b9ea12a9abda83240fd
Signed-off-by: Deepak Nibade <dnibade@nvidia.com>
Reviewed-on: http://git-master/r/1265185
Reviewed-on: http://git-master/r/1506359
(cherry picked from linux-4.9 commit be5331c94ebe9044cb67e3f622db517bfb7e28d4)
Reviewed-on: https://git-master.nvidia.com/r/1770149
Reviewed-by: Mikko Perttunen <mperttunen@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Timo Alho <talho@nvidia.com>
Tested-by: Timo Alho <talho@nvidia.com>
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>

2023-04-04 05:18:03 +00:00

..

governor_pod_scaling.c

devfreq: don't set last_scale for same freq

2023-04-04 05:18:03 +00:00

governor_wmark_active.c

devfreq: wmark: fix compilation on kernel 4.4

2023-04-04 05:18:03 +00:00

governor_wmark_simple.c

devfreq: wmark: fix compilation on kernel 4.4

2023-04-04 05:18:03 +00:00