Hi, Mark: Sorry to trouble you; I have a question about the regmap_add_irq_chip(): at present, we use the default primary interrupt handler to handle the parent interrupt from a mfd device;
I met a scenario: As soon as the interrupt is triggered, a wakelock is needed to be held until the threaded handler finishes, I think we may hold it in the primary interrupt handler, but now it's NULL by default; so could we make the the primary interrupt handler configurable? for example, add a parameter to regmap_add_irq_chip(), then the user can choose to use current solution or his/her own handler; what do you think? could you please share your opinion? thanks very much; -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
