diff options
| author | Viresh Kumar <viresh.kumar@linaro.org> | 2014-02-14 16:30:41 +0530 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2014-02-24 13:37:43 +0100 |
| commit | 1c0ca90207d61e4868043b5bbbbd7cc0bb1ac974 (patch) | |
| tree | 73f2451ba1511d9b6449061a142561a382e63fbd /tools/perf/scripts/python/check-perf-trace.py | |
| parent | d9a789c7a07e96eda7515e43932ee608dcece34d (diff) | |
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>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions