]> rtime.felk.cvut.cz Git - hercules2020/nv-tegra/linux-4.4.git/commit
devfreq: don't set last_scale for same freq
authorDeepak Nibade <dnibade@nvidia.com>
Mon, 5 Dec 2016 14:22:35 +0000 (19:52 +0530)
committermobile promotions <svcmobile_promotions@nvidia.com>
Wed, 14 Dec 2016 20:38:55 +0000 (12:38 -0800)
commit785bfd82d3fcf4d1bbaed1bdf4fd08e8e6f7864f
tree725b6c90585c0ea82035bb4296457d84597530ec
parentd68b41b28220b53365414d8c673feeb8aefa44f8
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-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Wen Yi <wyi@nvidia.com>
Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
drivers/devfreq/governor_pod_scaling.c