aboutsummaryrefslogtreecommitdiffstats
path: root/package/kernel/ep80579-drivers
diff options
context:
space:
mode:
authorJohn Crispin <john@openwrt.org>2016-03-03 20:24:47 +0000
committerJohn Crispin <john@openwrt.org>2016-03-03 20:24:47 +0000
commit4ac3411f09cc2a1a3ef32dfb656ba3b044f3f2e7 (patch)
tree407ddaf2221ac79063bce2bea14b1733cda6e5d7 /package/kernel/ep80579-drivers
parente4dc6acd31f03aace94e188d87fc90fd19e8f09e (diff)
downloadupstream-4ac3411f09cc2a1a3ef32dfb656ba3b044f3f2e7.tar.gz
upstream-4ac3411f09cc2a1a3ef32dfb656ba3b044f3f2e7.tar.bz2
upstream-4ac3411f09cc2a1a3ef32dfb656ba3b044f3f2e7.zip
kernel: gpio-button-hotplug: Add missing ONESHOT flag to threaded IRQ request
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
Diffstat (limited to 'package/kernel/ep80579-drivers')
0 files changed, 0 insertions, 0 deletions