Revert "Cpufreq: interactive: Check actual freq before setting new freq"
Puneet Saxena [Thu, 22 Aug 2013 12:52:39 +0000 (17:52 +0530)]
Browser P0 Benchmarks such as Sunspider, Panning
are regressed drastically by switching to new interactive
governor.
The score didn’t meet with the score achieved via older governor
though tweaked new governor knobs extremely.
Hence reverting new governor and bugfixes on it.

This reverts commit b89c138498dfa8db157c9b23172f9da98ea9e583.

Bug 1352880

Change-Id: I8548f5cef8557a26e110dd75ca739bf4c95287fe
Signed-off-by: Puneet Saxena <puneets@nvidia.com>
Reviewed-on: http://git-master/r/264925
Reviewed-by: Riham Haidar <rhaidar@nvidia.com>
Tested-by: Riham Haidar <rhaidar@nvidia.com>

drivers/cpufreq/cpufreq_interactive.c

index 48bb0be..41eb437 100644 (file)
@@ -429,12 +429,7 @@ static void cpufreq_interactive_timer(unsigned long data)
                pcpu->floor_validate_time = now;
        }
 
-       /* In case actual freq set in target(policy->cur) is not updated
-        * till next timer interrupt arrives, new_freq remains same as
-        * actual freq. Don't go for setting same frequency again.
-        */
-       if (pcpu->target_freq == new_freq
-               && pcpu->policy->cur == new_freq) {
+       if (pcpu->target_freq == new_freq) {
                trace_cpufreq_interactive_already(
                        data, cpu_load, pcpu->target_freq,
                        pcpu->policy->cur, new_freq);