What's the policy for interrupts that are detected by the interrupt controller on a channel that has disable_irq() in force? Should the device driver expect the interrupts to be lost? Or can it expect that they'll be remembered and that the CPU will process them when the IRQ channel is enabled? Furthermore, what about an interrupt that is already pending when disable_irq() is called? Is it okay for that to be discarded? Or must that be processed upon enable_irq()? MEI queried me about mn10300_cpupic_disable() in the MN10300 arch. It clears the channel enable bit and also clears the request and detect bits, thus losing any pending interrupt. Possibly I should introduce a separate shutdown() method that discards any pending interrupt and modify disable() to merely clear the enablement flag. I would guess, however, that some hardware may not remember interrupts that come in on disabled channels, in which case the driver cannot assume that interrupts won't be lost. Any thoughts? David -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html