On Sun, May 19, 2013 at 10:58:07PM -0700, Andrew Bresticker wrote: > request_threaded_irq() rejects calls which both do not specify a handler > (indicating that the primary IRQ handler should be used) and do not set > IRQF_ONESHOT because the combination is unsafe with level-triggered > interrupts. It is safe in this case, though, since max98090 IRQs are
Applied, thanks. If request_threaded_irq() is rejecting these that's not ideal - some threaded interrupts can only be generated from within threaded context and therefore can't have primary handlers. Unless it only rejects in the case where the parent IRQ is a hard IRQ of course.
signature.asc
Description: Digital signature
