Requesting any context irq is not actually great idea since threaded
interrupt handler is run at too unpredictable time which turns
timing information wrong. Fix it by requesting regular interrupt.

Signed-off-by: Ladislav Michl <la...@linux-mips.org>
---
 Changes:
 -v2: rebased to current linux.git

 drivers/media/rc/gpio-ir-recv.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/media/rc/gpio-ir-recv.c b/drivers/media/rc/gpio-ir-recv.c
index 733e4ed35078..110276d49495 100644
--- a/drivers/media/rc/gpio-ir-recv.c
+++ b/drivers/media/rc/gpio-ir-recv.c
@@ -161,7 +161,7 @@ static int gpio_ir_recv_probe(struct platform_device *pdev)
 
        platform_set_drvdata(pdev, gpio_dev);
 
-       rc = request_any_context_irq(gpio_to_irq(pdata->gpio_nr),
+       rc = request_irq(gpio_to_irq(pdata->gpio_nr),
                                gpio_ir_recv_irq,
                        IRQF_TRIGGER_FALLING | IRQF_TRIGGER_RISING,
                                        "gpio-ir-recv-irq", gpio_dev);
-- 
2.11.0

Reply via email to