> I wouldn't call this a "race." If the hardware sets the next status bit before the interrupt handler reaches the bottom of the loop, then the loop repeats, and the subsequent interrupt is reported as spurious. If the interrupt handler reaches the bottom of the loop before the hardware sets the next status bit, then the handler returns, and the subsequent interrupt is handled normally. Thus the handler is racing the hardware. > Sorry, don't understand. Isn't a spurious interrupt > reported per "nobody > cared" if an ISR returns IRQ_NONE? And the TMIO ISR never > does this. Is > the IRQ number, reported as spurious, that of TMIO? Is it > shared? tmio_mmc: Spurious irq, disabling! 0x00800780 0x833f0304 0x00000000 tmio_mmc: Spurious irq, disabling! 0x00800780 0x833f0304 0x00000000 tmio_mmc: Spurious irq, disabling! 0x00800780 0x833f0304 0x00000000 tmio_mmc: Spurious irq, disabling! 0x00800780 0x833f0304 0x00000000 tmio_mmc: Spurious irq, disabling! 0x00800780 0x833f0304 0x00000000 etc... Regards, Paul -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
