> > I think this can only work if we require .alert-handlers to start with a > > sanity check to make sure their device really raised an interrupt > > condition. And then return either -EBUSY or 0, similar to IRQ_HANDLED or > > IRQ_NONE. Or? > > I think so, but I am not sure if it is worth the effort. It would require > changing the API, and each driver supporting alert callbacks would have > to implement code to detect if it actually got an interrupt. The more I think about it, the more I like this proposal. I mean, irq subsystem has IRQ_NONE also for a reason. And we do not have that many alert handlers to convert. They could all return EBUSY by default because that is what they currently behave like anyhow. That being said, it will not be a top priority on my list.
Attachment:
signature.asc
Description: PGP signature
