On Fri, Jun 12, 2020 at 7:55 AM Jouko Haapaluoma <[email protected]> wrote: > > From: Jouko Haapaluoma <[email protected]> > > Make AT91 pinctrl driver compatible with ipipe > > Signed-off-by: Jouko Haapaluoma <[email protected]> > --- > drivers/pinctrl/pinctrl-at91.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/drivers/pinctrl/pinctrl-at91.c b/drivers/pinctrl/pinctrl-at91.c > index 50f0ec4..c4f60c7 100644 > --- a/drivers/pinctrl/pinctrl-at91.c > +++ b/drivers/pinctrl/pinctrl-at91.c > @@ -1582,6 +1582,7 @@ static struct irq_chip gpio_irqchip = { > .irq_unmask = gpio_irq_unmask, > /* .irq_set_type is set dynamically */ > .irq_set_wake = gpio_irq_set_wake, > + .flags = IRQCHIP_PIPELINE_SAFE, > }; > > static void gpio_irq_handler(struct irq_desc *desc) > @@ -1610,8 +1611,8 @@ static void gpio_irq_handler(struct irq_desc *desc) > } > > for_each_set_bit(n, &isr, BITS_PER_LONG) { > - generic_handle_irq(irq_find_mapping( > - gpio_chip->irq.domain, n)); > + ipipe_handle_demuxed_irq(irq_find_mapping( > + gpio_chip->irq.domain, n)); > } > } > chained_irq_exit(chip, desc); > -- > 2.2.2 > Everything looks good, did your testing include triggering any GPIO interrupts? I don't see any specific problems, just curious.
-Greg
