summaryrefslogtreecommitdiff
path: root/arch/arm/mach-mvebu/pmsu.c
diff options
context:
space:
mode:
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>2014-07-09 17:45:09 +0200
committerJason Cooper <jason@lakedaemon.net>2014-07-16 12:58:30 +0000
commit831e2518890f5ffd52706750b1cbf04feb2e7c59 (patch)
tree9cf81503b5447205c1a8e192336977ea7638bf44 /arch/arm/mach-mvebu/pmsu.c
parent7171511eaec5bf23fb06078f59784a3a0626b38f (diff)
downloadlinux-831e2518890f5ffd52706750b1cbf04feb2e7c59.tar.gz
linux-831e2518890f5ffd52706750b1cbf04feb2e7c59.tar.xz
ARM: mvebu: ensure CPU clocks are enabled
In the Armada XP SMP support code, we are reading the clock frequency of the booting CPU, and use that to assign the same frequency to the other CPUs, and we do this while the clocks are disabled. However, the CPU clocks are in fact never prepared/enabled, and to support cpufreq, we now have two code paths to change the frequency of the CPU clocks in the CPU clock driver: one when the clock is enabled (dynamic frequency scaling), one when the clock is disabled (adjusting the CPU frequency before starting the CPU). In order for this to work, the CPU clocks now have to be prepared and enabled after the initial synchronization of the clock frequencies is done, so that all future rate changes of the CPU clocks will trigger a dynamic frequency scaling transition. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Link: https://lkml.kernel.org/r/1404920715-19834-2-git-send-email-thomas.petazzoni@free-electrons.com Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'arch/arm/mach-mvebu/pmsu.c')
0 files changed, 0 insertions, 0 deletions