On Sun, 2010-09-12 at 11:54 -0500, Josh Cartwright wrote: > That's up for you, the driver writer, to decide. In your driver code > you are probably already keeping around a per-device object (that will > hold pointers to mapped registers, or other ways of communicating with > your device), so it makes sense in this case to request_irq() by passing > a pointer to that per-device object. In this way, your handler can > communicate with your device and ask it if it was the one that generated > the interrupt. Wow, very clear :) Thank you, -- Carlo -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
