On Sep 12, 2010, at 5:08 PM, Josh Cartwright wrote: > The provided dev pointer to request_irq() is not itself useful to the > core IRQ code, it doesn't do anything but store it away for use when > calling your handler function. Ok > That being said, the IRQ-core core does need some way to differentiate > between handlers for shared IRQs. This is necessary so that you can > selectively uninstall handlers. This is also why the free_irq() takes > not only the IRQ#, but the dev_id (your dev1 or dev2) you registered > with. I'm ok also with this point. But for example: the IRQ-core code executes both the handlers for the shared irqn. Just one of the handlers is the right one for that specific device, whereas the other one should be return IRQ_NONE. How do those parameters dev1 and dev2 help me within the handler functions to know if the interrupt is coming from the right devices? > Hopefully that answers your question. :) I hope I'm not saying something stupid :) -- Carlo Caione -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
