hi, On Tue, Sep 27, 2011 at 05:38:51PM +0300, Tero Kristo wrote: > > 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
do you remember what was the reason for that being turned down ? Maybe I can search the archives... > the irq_desc allocation mechanism should be dynamic... there are some > 200 programmable pads anyway. I wouldn't worry too much about that. If you try to allocate irq_desc dynamically, you would have to keep track of an "irq_base" for each irq_desc you allocate, otherwise it's difficult to map it back to mux number. -- balbi
signature.asc
Description: Digital signature
