On 12/29/2010 10:27 PM, Rabin Vincent wrote:On Thu, Dec 30, 2010 at 10:59 AM, Abhijeet DharmapurikarSince GIC doesnt have disable callback it implements lazy disabling. The
There are some interrupts that are true edge triggered in nature. If not
marked IRQ_PENDING, when disabled, they will be lost.
Use the set_type callback to assign the correct flow type handler for
shared peripheral interrupts.
Signed-off-by: Abhijeet Dharmapurikar<adharmap@xxxxxxxxxxxxxx>
This came to light when a edge triggered interrupt was supposed to
sytem. The flow handler was set to the default handle_level_irq. On
path the flow handler was invoked right after the I bit was cleared
each individual interrupts were enabled. This made the
Why does the flow handler hit when the interrupt is disabled? Have you
IRQF_NOSUSPEND on this interrupt?
interrupt is only marked IRQ_DISABLED in the descriptor but is not
masked in the GIC. Hence the interrupt flow handler is hit.
Now that I re-read the code setting IRQF_NO_SUSPEND would fix the issue.