cpufreq: interactive: base hispeed bump on target freq, not actual
authorTodd Poynor <toddpoynor@google.com>
Thu, 19 Apr 2012 19:52:48 +0000 (12:52 -0700)
committerArve Hjønnevåg <arve@android.com>
Mon, 1 Jul 2013 20:40:43 +0000 (13:40 -0700)
commit2e2151f88b05e1bf51191d6b84d33c618a875492
treeb9084ad2ad88519e1dd7017f7dbfe4ea1e6f9e55
parentcdd48fc92e988c0d09aa0228a88fd00500dc0e00
cpufreq: interactive: base 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