summaryrefslogtreecommitdiff
path: root/drivers/clocksource/exynos_mct.c
diff options
context:
space:
mode:
authorViresh Kumar <viresh.kumar@linaro.org>2013-07-02 16:36:28 +0530
committerMarek Szyprowski <m.szyprowski@samsung.com>2014-04-01 13:07:34 +0200
commit56e69b35155ea6b699c6dba228aae5521fa8d4a2 (patch)
tree7882c48df18534160c19e18bbfca9dbb7bd3e790 /drivers/clocksource/exynos_mct.c
parentf561427a7dbfd94e20b69e062d4b1c0ffc93d996 (diff)
downloadlinux-3.10-56e69b35155ea6b699c6dba228aae5521fa8d4a2.tar.gz
linux-3.10-56e69b35155ea6b699c6dba228aae5521fa8d4a2.tar.bz2
linux-3.10-56e69b35155ea6b699c6dba228aae5521fa8d4a2.zip
cpufreq: Fix serialization of frequency transitions
Commit 7c30ed ("cpufreq: make sure frequency transitions are serialized") interacts poorly with systems that have a single core freqency for all cores. On such systems we have a single policy for all cores with several CPUs. When we do a frequency transition the governor calls the pre and post change notifiers which causes cpufreq_notify_transition() per CPU. Since the policy is the same for all of them all CPUs after the first and the warnings added are generated by checking a per-policy flag the warnings will be triggered for all cores after the first. Fix this by allowing notifier to be called for n times. Where n is the number of cpus in policy->cpus. Change-Id: I5712dde7f992644f9c3ddc8313151f80bea0d877 Reported-and-tested-by: Mark Brown <broonie@linaro.org> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/clocksource/exynos_mct.c')
0 files changed, 0 insertions, 0 deletions