cpufreq: interactive: based hispeed bump on target freq, not actual
authorTodd Poynor <toddpoynor@google.com>
Thu, 19 Apr 2012 19:52:48 +0000 (12:52 -0700)
committerTodd Poynor <toddpoynor@google.com>
Fri, 20 Apr 2012 02:45:37 +0000 (19:45 -0700)
commit4e3800ea447962106a962f5279ea508edd6ca160
treec8d2685541250b04aad114312b1265c3ad2dd38c
parent94225ab0bef6f32108eaa410bb894caa2b4317e2
cpufreq: interactive: based hispeed bump on target freq, not actual

For systems that set a common speed for all CPUs, checking current
speed here could bypass the intermediate hispeed bump decision for
this CPU when another CPU was already at hispeed.  This could
result in an overly high setting (for all CPUs) in situations
where all CPUs were about to drop to load levels that map to
hispeed or below.

Change-Id: I186f23dcfc5e2b6336cab8b0327f0c8a9a4482bc
Signed-off-by: Todd Poynor <toddpoynor@google.com>
drivers/cpufreq/cpufreq_interactive.c