On Saturday 28 February 2009, Stefan Richter wrote: > David Brownell wrote: > > The other is that Linux needs real support for threaded > > interrupts. Almost every I2C (or SPI) device that raises > > an IRQ needs its IRQ handler to run in a thread, and most > > of them have the same type of workqueue-based hack to > > get such a thread. (Some others have bugs instead...) > > Since when is having an IRQ handler scheduling a workqueue job a hack? The only "hack" I recall mentioning was the need to forcibly re-enable IRQs that lockdep wrongly disabled. > In kernels whose IRQ handlers don't sleep, we don't pretend that they > could; instead we defer sleeping work to a context which can sleep. > > Or from another angle: If a driver requires a kernel with sleeping IRQ > handlers, why submit it for inclusion into a kernel which does not (yet) > provide nonatomic context to IRQ handlers? Or from yet another angle: how will progress ever happen if nobody pushes the boundaries? :) We've known for ages that threaded IRQs will eventually show up in mainline. Better IMO to plan for that, and expect minor changes to the drivers which have needed them all along. - Dave -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
