disable_irq() causes hang on AT91RM9200 targets?
Guys:
Has anyone noticed that with 2.6.33-rc5 (at least) on AT91RM9200, disable_irq() seems to cause a lockup when the interrupt number is a GPIO line? I'm calling disable_irq() from an interrupt handler on the same GPIO line.
I just saw this happen, and it seems to be repeatable. Just wondering if this is a known issue before I start digging into it...
b.g.
Signature · 2 lines
Bill Gatliff bgat at billgatliff.com
Quoted 11 lines · Bill Gatliff
Guys:
Has anyone noticed that with 2.6.33-rc5 (at least) on AT91RM9200,
disable_irq()seems to cause a lockup when the interrupt number is a GPIO line? I'm callingdisable_irq()from an interrupt handler on the same GPIO line.I just saw this happen, and it seems to be repeatable. Just wondering if this is a known issue before I start digging into it...
Heh, disable_irq_nosync(). D'oh! :)
b.g.
Signature · 2 lines
Bill Gatliff bgat at billgatliff.com
Quoted 10 lines · Bill Gatliff
Guys:
Has anyone noticed that with 2.6.33-rc5 (at least) on AT91RM9200,
disable_irq()seems to cause a lockup when the interrupt number is a GPIO line? I'm callingdisable_irq()from an interrupt handler on the same GPIO line.I just saw this happen, and it seems to be repeatable. Just wondering if this is a known issue before I start digging into it...
disable_irq_nosync(), disable_irq() has for a while waited for the IRQ to clear before exiting. Now, guess what happens if you wait for the IRQ to clear in the IRQ handler that is currently executing.
Quoted 13 lines
b.g.
Signature · 9 lines
Bill Gatliff bgat at billgatliff.com _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel at lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Signature · 5 lines
-- Ben Q: What's a light-year? A: One-third less calories than a regular year.
Hello,
Quoted 9 lines · Bill Gatliff
Quoted 8 lines · Bill Gatliff
Guys:
Has anyone noticed that with 2.6.33-rc5 (at least) on AT91RM9200,
disable_irq()seems to cause a lockup when the interrupt number is a GPIO line? I'm callingdisable_irq()from an interrupt handler on the same GPIO line.
Quoted 5 lines
Quoted 3 lines
I just saw this happen, and it seems to be repeatable. Just wondering if this is a known issue before I start digging into it...
Heh,
disable_irq_nosync(). D'oh! :)
Can make this a bit more verbose:
[ ] After switching from disable_irq to disable_irq_nosync it magically
works.
[ ] Of course I know not to use disable_irq in irq context. I meant it
causes a lockup when I use *disable_irq_nosync* in irq context.
Best regards
Uwe
Signature · 2 lines
Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |