cpufreq: interactive: prevents the frequency to directly raise above the hispeed_freq from a lower frequency.
When the load was below go_hispeed_load, there is a possibility that choose_freq() would return a frequency which would be higher than the hispeed_freq. According to the policy we should first jump to the hispeed_freq, stay there for above_hispeed_delay and then be allowed to raise higher than that. Added a check to prevent the frequency to be directly raised to something higher than the hispeed_freq. Change-Id: Icda5d848dd9beadcc18835082ddf269732c75bd0 Signed-off-by: Ruchi Kandoi <kandoiruchi@google.com>
This commit is contained in:
parent
61a37b31dc
commit
bc88e631b2
1 changed files with 3 additions and 0 deletions
|
@ -377,6 +377,9 @@ static void cpufreq_interactive_timer(unsigned long data)
|
|||
}
|
||||
} else {
|
||||
new_freq = choose_freq(pcpu, loadadjfreq);
|
||||
if (new_freq > tunables->hispeed_freq &&
|
||||
pcpu->target_freq < tunables->hispeed_freq)
|
||||
new_freq = tunables->hispeed_freq;
|
||||
}
|
||||
|
||||
if (pcpu->target_freq >= tunables->hispeed_freq &&
|
||||
|
|
Loading…
Add table
Reference in a new issue