aboutsummaryrefslogtreecommitdiff
path: root/drivers/bus/mvebu-mbus.c
diff options
context:
space:
mode:
authorMagnus Damm <damm+renesas@opensource.se>2015-01-16 10:49:19 +0900
committerSimon Horman <horms+renesas@verge.net.au>2015-01-17 09:28:41 +0900
commitf469cde20a7ee342070b4a459b6fce469a3186db (patch)
tree1d75df70458ba48e2269c58231686cc653dbfe48 /drivers/bus/mvebu-mbus.c
parent1fbbc3f0c5440a4c674b3d6de0a9dd447666b508 (diff)
downloadlinux-f469cde20a7ee342070b4a459b6fce469a3186db.tar.gz
ARM: shmobile: r8a7779: Instantiate GIC from C board code in legacy builds
As of commit 9a1091ef0017c40a ("irqchip: gic: Support hierarchy irq domain."), Marzen legacy hangs during boot with: Image Name: 'Linux-3.19.0-rc4' Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3445880 Bytes = 3.3 MiB Load Address: 60008000 Entry Point: 60008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Enabling DEBUG_LL does not seem to change the situation, however this patch by itself fixes this issue and re-enables normal boot. This issue happens because the IRQ numbers of the GIC are now virtual, and no longer match the hardcoded hardware IRQ numbers in the platform board code. To fix this, instantiate the GIC from platform board code when compiling a legacy kernel, like is done for the sh73a0, r8a7740 and r8a7778 legacy code. Follows same style as the r8a7740 legacy GIC fix by Geert Uytterhoeven, thanks to him for the initial work. Signed-off-by: Magnus Damm <damm+renesas@opensource.se> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Diffstat (limited to 'drivers/bus/mvebu-mbus.c')
0 files changed, 0 insertions, 0 deletions