On Tue, 2011-09-27 at 15:24 +0200, Balbi, Felipe wrote: > Hi, > > On Tue, Sep 27, 2011 at 06:48:35PM +0530, Munegowda, Keshava wrote: > > > So, you would need a mechanism to do something like this: > > > > > > pad a or b wakeup detected -> irq0 > > > pad c or d wakeup detected -> irq1? > > > > yes, if get something like this , its perfect. > > can't you have different IRQs for each pad ? I mean, allocate one > irq_desc for each pad and let drivers request a pad/pin as an IRQ > source. Then, when you detect a pad wakeup, you can: Direct pad to irq mapping was turned down on some previous version of the prcm chain handler set, but yes, it is a potential approach. However the irq_desc allocation mechanism should be dynamic... there are some 200 programmable pads anyway. > > unsigned pad_irq = pad_number - pad->irq_base; > > handle_nested_thread(pad_irq); > > this will make use of threaded IRQ handlers even. Could it be something > like that ? > Texas Instruments Oy, Tekniikantie 12, 02150 Espoo. Y-tunnus: 0115040-6. Kotipaikka: Helsinki -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
