summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-mvebu/Kconfig
diff options
context:
space:
mode:
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>2013-03-21 17:59:15 +0100
committerJason Cooper <jason@lakedaemon.net>2013-04-15 14:06:16 +0000
commit87e1bed4067e33a4636bffc03689ffb045d586d6 (patch)
treedbc92ffcfd5e90fbdce15689cf0f6113a05d7e24 /arch/arm/mach-mvebu/Kconfig
parenta33dc586c90ef8eee273280782b43b40cd43ad7e (diff)
downloadlinux-stable-87e1bed4067e33a4636bffc03689ffb045d586d6.tar.gz
linux-stable-87e1bed4067e33a4636bffc03689ffb045d586d6.tar.bz2
linux-stable-87e1bed4067e33a4636bffc03689ffb045d586d6.zip
arm: mach-mvebu: convert to use mvebu-mbus driver
The changes needed to migrate the mach-mvebu (Armada 370 and Armada XP) to the mvebu-mbus driver are fairly minimal, since not many devices currently supported on those SoCs use address decoding windows. The only one being the BootROM window, used to bring up secondary CPUs. However, this BootROM window needed for SMP brings an important requirement: the mvebu-mbus driver must be initialized at the ->early_init() time, otherwise the BootROM window cannot be setup early enough to be ready before the secondary CPUs are started. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'arch/arm/mach-mvebu/Kconfig')
-rw-r--r--arch/arm/mach-mvebu/Kconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm/mach-mvebu/Kconfig b/arch/arm/mach-mvebu/Kconfig
index 440b13ef1fed..c3715a536d87 100644
--- a/arch/arm/mach-mvebu/Kconfig
+++ b/arch/arm/mach-mvebu/Kconfig
@@ -13,6 +13,7 @@ config ARCH_MVEBU
select MVEBU_CLK_CORE
select MVEBU_CLK_CPU
select MVEBU_CLK_GATING
+ select MVEBU_MBUS
if ARCH_MVEBU