Commit d9e4ad5b authored by David Woodhouse's avatar David Woodhouse Committed by Thomas Gleixner

Document that IRQ_NONE should be returned when IRQ not actually handled

Our IRQ storm detection works when an interrupt handler returns
IRQ_NONE for thousands of consecutive interrupts in a second. It
doesn't hurt to occasionally return IRQ_NONE when the interrupt is
actually genuine.

Drivers should only be returning IRQ_HANDLED if they have actually
*done* something to stop an interrupt from happening — it doesn't just
mean "this really *was* my device".
Signed-off-by: default avatarDavid Woodhouse <David.Woodhouse@intel.com>
Cc: davem@davemloft.net
Link: http://lkml.kernel.org/r/1446016471.3405.201.camel@infradead.orgSigned-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
parent 3b93baf5
...@@ -3,7 +3,7 @@ ...@@ -3,7 +3,7 @@
/** /**
* enum irqreturn * enum irqreturn
* @IRQ_NONE interrupt was not from this device * @IRQ_NONE interrupt was not from this device or was not handled
* @IRQ_HANDLED interrupt was handled by this device * @IRQ_HANDLED interrupt was handled by this device
* @IRQ_WAKE_THREAD handler requests to wake the handler thread * @IRQ_WAKE_THREAD handler requests to wake the handler thread
*/ */
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment