[ACPI] Always set P-state on initialization
authorDominik Brodowski <linux@dominikbrodowski.net>
Wed, 18 May 2005 17:49:00 +0000 (13:49 -0400)
committerLen Brown <len.brown@intel.com>
Fri, 29 Jul 2005 22:29:47 +0000 (18:29 -0400)
Otherwise a platform that supports ACPI based cpufreq
and boots up at lowest possible speed could stay there
forever.  This because the governor may request max speed,
but the code doesn't update if there is no change in
speed, and it assumed the initial state of max speed.

http://bugzilla.kernel.org/show_bug.cgi?id=4634

Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c

index 963e17aa205d60ea91977887c622e6c4cb4c2701..60a9e54dd20ee25d223385d2fcc47c7858a5893b 100644 (file)
@@ -442,6 +442,13 @@ acpi_cpufreq_cpu_init (
                        (u32) data->acpi_data.states[i].transition_latency);
 
        cpufreq_frequency_table_get_attr(data->freq_table, policy->cpu);
+       
+       /*
+        * the first call to ->target() should result in us actually
+        * writing something to the appropriate registers.
+        */
+       data->resume = 1;
+       
        return (result);
 
  err_freqfree: