On Sun, 18 Apr 2010 21:14:12 +0200 (CEST)
Thomas Gleixner t...@linutronix.de wrote:
On Sun, 18 Apr 2010, Guillaume Knispel wrote:
Now everything seems to work fine: my device was not previously not
interrupting anymore after typically 1 or 2 minutes (because the
interrupt signal stays at
Hi,
From reading the code (kernel/irq stuffs), it seems that at least some
handle_edge_irq based interrupts are not replayed when enabling if
desc-chip-retrigger == NULL and on a platform where
CONFIG_HARDIRQS_SW_RESEND is not set (which for now is only defined for
(some?) arm and avr32).
On Sun, 18 Apr 2010 05:34:39 +0200
Guillaume Knispel gknis...@proformatique.com wrote:
From reading the code (kernel/irq stuffs), it seems that at least some
handle_edge_irq based interrupts are not replayed when enabling if
desc-chip-retrigger == NULL and on a platform where
On Sun, 18 Apr 2010, Guillaume Knispel wrote:
Now everything seems to work fine: my device was not previously not
interrupting anymore after typically 1 or 2 minutes (because the
interrupt signal stays at level low until the device is served, so
So you are having a level interrupt device and
