Improving lost and spurious IRQ handling

Posted Jun 18, 2010 21:20 UTC (Fri) by giraffedata (guest, #1954)
Parent article: Improving lost and spurious IRQ handling

When the operation is completed, unexpect_irq() should be called, with timedout indicating whether the operation timed out (the interrupt did not arrive)

Does this mean the device driver should call unexpect_irq()? How does it know the interrupt did not arrive, given that someone calls the driver's interrupt handler (because of expect_irq()) even if it didn't?