Commit 0063a340 authored Mar 21, 2013 by Todd Poynor Committed by Amit Pundir Oct 24, 2016

cpufreq: interactive: base above_hispeed_delay on target freq, not current



Time to wait should be based on the intended target speed, not the
actual speed (which may be held high by another CPU).

Change-Id: Ifc5bb55d06adddb9a02af90af05398a78f282272
Reported-by: Arve Hjønnevåg <arve@android.com>
Signed-off-by: Todd Poynor <toddpoynor@google.com>

parent 5fc17adf

drivers/cpufreq/cpufreq_interactive.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -377,7 +377,7 @@ static void cpufreq_interactive_timer(unsigned long data)
		if (pcpu->target_freq >= hispeed_freq &&
		new_freq > pcpu->target_freq &&
		now - pcpu->hispeed_validate_time <
		freq_to_above_hispeed_delay(pcpu->policy->cur)) {
		freq_to_above_hispeed_delay(pcpu->target_freq)) {
		trace_cpufreq_interactive_notyet(
		data, cpu_load, pcpu->target_freq,
		pcpu->policy->cur, new_freq);