Re: [PATCH 5/7] omap:mailbox-resolve multiple receiver problem

2010-10-29 Thread Hari Kanigeri
Omar, >> OMAP4 shares one interrupt line for all the mailbox instances. >> The ISR is handling only the mailbox instance that was registered last. > > This shouldn't be needed, request_irq is being called with IRQF_SHARED flag > and different device ids, so if a message arrives it fires an interr

Re: [PATCH 5/7] omap:mailbox-resolve multiple receiver problem

2010-10-28 Thread Omar Ramirez Luna
On 10/14/2010 9:13 PM, Kanigeri, Hari wrote: OMAP4 shares one interrupt line for all the mailbox instances. The ISR is handling only the mailbox instance that was registered last. This shouldn't be needed, request_irq is being called with IRQF_SHARED flag and different device ids, so if a mess

[PATCH 5/7] omap:mailbox-resolve multiple receiver problem

2010-10-14 Thread Hari Kanigeri
OMAP4 shares one interrupt line for all the mailbox instances. The ISR is handling only the mailbox instance that was registered last. So if both mailbox instances are running at the same time, the first mailbox that registered wouldn't get the mailbox message. The same issue is present in Transmit

[PATCH 5/7] omap:mailbox-resolve multiple receiver problem

2010-10-14 Thread Hari Kanigeri
OMAP4 shares one interrupt line for all the mailbox instances. The ISR is handling only the mailbox instance that was registered last. So if both mailbox instances are running at the same time, the first mailbox that registered wouldn't get the mailbox message. The same issue is present in Transmit

[PATCH 5/7] omap:mailbox-resolve multiple receiver problem

2010-10-13 Thread Hari Kanigeri
OMAP4 shares one interrupt line for all the mailbox instances. The ISR is handling only the mailbox instance that was registered last. So if both mailbox instances are running at the same time, the first mailbox that registered wouldn't get the mailbox message. The same issue is present in Transmit