On Fri, Jul 25, 2014 at 02:47:25PM +0200, Rafael J. Wysocki wrote: > So it looks like we really need the "suspend" thing to either disable > the interrupt entirely (in which case all handlers for all actions > will not be invoked after it's been suspended) or leave it enabled > (causing all handlers to be invoked all the time). > > I'm not sure if we can do much beyond what's already in your tree > about that, then. > > Well, perhaps the patch failing the irq request in case of the > IRQF_NO_SUSPEND mismatch is a bit too drastic. Instead, we could > just print a warning in __setup_irq() in that case and then check > IRQF_NO_SUSPEND for all actions in __disable_irq(). > > What about this?
I suppose, not failing the request_irq allows the machine to boot and mostly work, any funnies will be when the machine gets suspended. And disabling suspend might be overkill because it might just all work anyhow because the user didn't need that one particular wakeup source. What a terrible mess this. -- 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/
