summaryrefslogtreecommitdiff
path: root/arch/arm/mach-exynos/Kconfig
diff options
context:
space:
mode:
authorNicolas Pitre <nicolas.pitre@linaro.org>2014-06-24 18:36:32 +0100
committerRussell King <rmk+kernel@arm.linux.org.uk>2014-07-18 11:58:04 +0100
commitfbb0499091dc1132995214a47188214602fd75c9 (patch)
treeadae97ca27e1ac6823943156dac3c96729c3872c /arch/arm/mach-exynos/Kconfig
parent3592d7e002438980f9ce4a399f21ec94cbf071ea (diff)
ARM: 8083/1: exynos: activate the CCI on boot CPU/cluster using the MCPM loopback
The Chromebook firmware doesn't enable the CCI for the boot cpu, and arguably it shouldn't have to either. Let's have the kernel handle the CCI on its own for the boot CPU the same way it does it for secondary CPUs by using the MCPM loopback. This allows to boot all 8 cores on exynos5420-peach-pit, exynos5800-peach-pi and ARM Chromebook 2. Signed-off-by: Nicolas Pitre <nico@linaro.org> Tested-by: Tushar Behera <tushar.b@samsung.com> Reviewed-by: Kevin Hilman <khilman@linaro.org> Tested-by: Kevin Hilman <khilman@linaro.org> Tested-by: Doug Anderson <dianders@chromium.org> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'arch/arm/mach-exynos/Kconfig')
0 files changed, 0 insertions, 0 deletions