cpufreq: interactive: resched timer if max freq raised
authorLianwei Wang <a22439@motorola.com>
Fri, 26 Apr 2013 05:30:51 +0000 (13:30 +0800)
committerRiham Haidar <rhaidar@nvidia.com>
Fri, 26 Jul 2013 20:50:20 +0000 (13:50 -0700)
commitba483d38dd783c45118cf66dcd9a23008d68571c
treebc395b07e67ab06a7d808cfd46907db65d702583
parentfb20d6e49a0987169abac109d689de4c9d829fbf
cpufreq: interactive: resched timer if max freq raised

When the policy max freq is raised, and before the timer is
rescheduled in idle callback, the cpu freq may stuck at a
lower freq.

The target_freq shall be updated too, else on a high load
situation, the new_freq is always equal to target_freq and
which will cause freq stuck at a lower freq too.

Reschedule the timer on gov limits callback.

Bug 1316765

Change-Id: I6c187001ab43e859731429b64f75a74eebc37a24
Signed-off-by: Lianwei Wang <a22439@motorola.com>
(cherry picked from commit 0edc2b4c9c30a695d9500d3204acdf5f3ddfa027)
Signed-off-by: Puneet Saxena <puneets@nvidia.com>
Reviewed-on: http://git-master/r/251584
Reviewed-by: Elaine Tam <etam@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Jay Cheng <jacheng@nvidia.com>
Reviewed-by: Venkata (Muni) Anda <vanda@nvidia.com>
Tested-by: Elaine Tam <etam@nvidia.com>
drivers/cpufreq/cpufreq_interactive.c