On Tue, 8 Dec 2015, Thomas Petazzoni wrote: > When a device driver uses a normal (non per-CPU) interrupt, then it > doesn't have to take care of disabling the interrupt on suspend and > re-enabling the interrupt on resume at the interrupt controller level. > This is all transparently handled by the irqchip driver. > > Why should the handling of per-CPU interrupts be different and require > explicit handling from each device driver rather than being > transparently handled by the irqchip driver ?
Fair enough. Did not think about the boot cpu part. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/