Actually, the longer I think about it, the more it converges in complexity
to disable_irq (assuming useful semantics - you can do better if you make
the whole thing much harder to use, surprise ;-), so maybe this is the
answer ...
> It might even be possible to allow the other driver on a shared interrupt
> to continue to get interrupts with a scheme like this as long as an
> interrupt didn't come in for the device that's blocked.
Hmm, with a per-handler did_I_do_it function ? Sounds complex.
- Werner
-- _________________________________________________________________________ / Werner Almesberger, ICA, EPFL, CH werner.almesberger@ica.epfl.ch / /_IN_R_131__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/