summaryrefslogtreecommitdiffstats
path: root/kernel/backtracetest.c
diff options
context:
space:
mode:
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>2014-04-22 23:26:26 +0200
committerJason Cooper <jason@lakedaemon.net>2014-04-26 19:45:06 +0000
commitdeac3d874ea1e1ef50604cec33ddfb01edb0c976 (patch)
tree7524fce14d00fb8d76cb56ac453f36517889d3fd /kernel/backtracetest.c
parent0180ed45da5198e0e7362c56b3a107d3278666f6 (diff)
downloadblackbird-op-linux-deac3d874ea1e1ef50604cec33ddfb01edb0c976.tar.gz
blackbird-op-linux-deac3d874ea1e1ef50604cec33ddfb01edb0c976.zip
ARM: orion: switch to a per-platform handle_irq() function
Moving to the Device Tree implies having CONFIG_MULTI_IRQ_HANDLER enabled, even for non-DT platforms (if we want both DT and non-DT platforms to be supported in a single kernel). However, the common CONFIG_MULTI_IRQ_HANDLER handler for non-DT platforms in plat-orion/irq.c doesn't match the needs of Orion5x. Also, it doesn't make much sense for orion_irq_init() to register the multi-IRQ handler: orion_irq_init() is called once for each IRQ cause/mask tuple, while the multi-IRQ handler only needs to be registered once. To solve this problem, we move the multi-IRQ handle in per-platform code: mach-kirkwood/irq.c and mach-dove/irq.c. The Orion5x variant will be introduced in a followup commit. Of course, this code will ultimately be completely removed once all boards are converted to the Device Tree. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> Link: https://lkml.kernel.org/r/1398202002-28530-23-git-send-email-thomas.petazzoni@free-electrons.com Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'kernel/backtracetest.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud