4ac3411f09
Without the IRQF_ONESHOT flag in devm_request_threaded_irq() call I get following error: genirq: Threaded irq requested with handler=NULL and !ONESHOT for irq 56 gpio-keys gpio-keys: failed to request irq:56 for gpio:20 >From kernel/irq/manage.c: The interrupt was requested with handler = NULL, so we use the default primary handler for it. But it does not have the oneshot flag set. In combination with level interrupts this is deadly, because the default primary handler just wakes the thread, then the irq lines is reenabled, but the device still has the level irq asserted. Rinse and repeat.... While this works for edge type interrupts, we play it safe and reject unconditionally because we can't say for sure which type this interrupt really has. The type flags are unreliable as the underlying chip implementation can override them. Signed-off-by: Petr Štetiar <ynezz@true.cz> SVN-Revision: 48894 |
||
|---|---|---|
| .. | ||
| acx-mac80211 | ||
| ar7-atm | ||
| avila-wdt | ||
| brcm2708-gpu-fw | ||
| broadcom-wl | ||
| button-hotplug | ||
| ep80579-drivers | ||
| gpio-button-hotplug | ||
| hostap-driver | ||
| i2c-gpio-custom | ||
| lantiq | ||
| linux | ||
| mac80211 | ||
| mmc_over_gpio | ||
| mt76 | ||
| mwlwifi | ||
| om-watchdog | ||
| rotary-gpio-custom | ||
| rtc-rv5c386a | ||
| spi-gpio-custom | ||
| trelay | ||
| w1-gpio-custom | ||
| wrt55agv2-spidevs | ||