summaryrefslogtreecommitdiffstats
path: root/Makefile
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2012-10-16 15:07:49 -0700
committerThomas Gleixner <tglx@linutronix.de>2012-11-01 12:11:31 +0100
commit293a7a0a165c4f8327bbcf396cee9ec672727c98 (patch)
tree6f4dca36e85e5d7cd3648bb322b7db9c29fb8c85 /Makefile
parent1e207eb1c3f0e8b690401f02fe08e7b53903f010 (diff)
downloadop-kernel-dev-293a7a0a165c4f8327bbcf396cee9ec672727c98.zip
op-kernel-dev-293a7a0a165c4f8327bbcf396cee9ec672727c98.tar.gz
genirq: Provide means to retrigger parent
Attempts to retrigger nested threaded IRQs currently fail because they have no primary handler. In order to support retrigger of nested IRQs, the parent IRQ needs to be retriggered. To fix, when an IRQ needs to be resent, if the interrupt has a parent IRQ and runs in the context of the parent IRQ, then resend the parent. Also, handle_nested_irq() needs to clear the replay flag like the other handlers, otherwise check_irq_resend() will set it and it will never be cleared. Without clearing, it results in the first resend working fine, but check_irq_resend() returning early on subsequent resends because the replay flag is still set. Problem discovered on ARM/OMAP platforms where a nested IRQ that's also a wakeup IRQ happens late in suspend and needed to be retriggered during the resume process. [khilman@ti.com: changelog edits, clear IRQS_REPLAY in handle_nested_irq()] Reported-by: Kevin Hilman <khilman@ti.com> Tested-by: Kevin Hilman <khilman@ti.com> Cc: linux-arm-kernel@lists.infradead.org Link: http://lkml.kernel.org/r/1350425269-11489-1-git-send-email-khilman@deeprootsystems.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud