summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-orion5x/board-dt.c
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-orion5x/board-dt.c
parenta33dc586c90ef8eee273280782b43b40cd43ad7e (diff)
downloadblackbird-op-linux-87e1bed4067e33a4636bffc03689ffb045d586d6.tar.gz
blackbird-op-linux-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-orion5x/board-dt.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud