Use the IRQ handler field that's available in the struct gpio_irq_chip
when allocating an IRQ rather than hardcoding the handler to
handle_bad_irq(). The kernel reboots without any messages when testing
this using spmi-gpio on the Nexus 5.
Signed-off-by: Brian Masney <[email protected]>
---
I didn't have time to dig into more detail about why this is happening.
I suspect the issue is that __irq_do_set_handler() has a special check
for handle_bad_irq:
https://elixir.bootlin.com/linux/latest/source/kernel/irq/chip.c#L974
My post about this:
https://lore.kernel.org/linux-gpio/[email protected]/
drivers/gpio/gpiolib.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index 5423242deb81..bc68ebb8f40e 100644
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -1872,7 +1872,7 @@ static int gpiochip_hierarchy_irq_domain_alloc(struct irq_domain *d,
hwirq + i,
gc->irq.chip,
gc,
- handle_bad_irq,
+ girq->handler,
NULL, NULL);
irq_set_probe(irq + i);
--
2.20.1