cpufreq: don't call cpufreq_update_policy() on CPU addition
authorViresh Kumar <viresh.kumar@linaro.org>
Fri, 14 Feb 2014 11:00:41 +0000 (16:30 +0530)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Mon, 24 Feb 2014 12:37:43 +0000 (13:37 +0100)
commit1c0ca90207d61e4868043b5bbbbd7cc0bb1ac974
tree73f2451ba1511d9b6449061a142561a382e63fbd
parentd9a789c7a07e96eda7515e43932ee608dcece34d
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 <viresh.kumar@linaro.org>
Reviewed-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
drivers/cpufreq/cpufreq.c