From: Viresh Kumar Date: Fri, 14 Feb 2014 11:00:41 +0000 (+0530) Subject: cpufreq: don't call cpufreq_update_policy() on CPU addition X-Git-Tag: v3.15-rc1~151^2~2^2~9^2~11^2~8^2 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1c0ca90207d61e4868043b5bbbbd7cc0bb1ac974;p=pandora-kernel.git cpufreq: don't call cpufreq_update_policy() on CPU addition cpufreq_update_policy() is called from two places currently. From a workqueue handled queued from cpufreq_bp_resume() for boot CPU and from cpufreq_cpu_callback() whenever a CPU is added. The first one makes sure that boot CPU is running on the frequency present in policy->cpu. But we don't really need a call from cpufreq_cpu_callback(), because we always call cpufreq_driver->init() (which will set policy->cur correctly) whenever first CPU of any policy is added back. And so every policy structure is guaranteed to have the right frequency in policy->cur. Signed-off-by: Viresh Kumar Reviewed-by: Srivatsa S. Bhat Signed-off-by: Rafael J. Wysocki --- Reading git-diff-tree failed