On Thu, Mar 16, 2017 at 12:17:45PM -0700, Tony Lindgren wrote: > Hmm maybe we need to flush posted writes when re-enabling the GPIO interrupts? > > Below is an untested patch that might help if that's the case. Unfortunately that's not the case. Even writing set&clear version of interrupt demux handler did not make it any better. And idea from ancient patch I initially sent is not easily extensible when we need to trigger interrupt on both edges. So far I'm clueless... ladis > Regards, > > Tony > > 8< -------------------------- > diff --git a/drivers/gpio/gpio-omap.c b/drivers/gpio/gpio-omap.c > --- a/drivers/gpio/gpio-omap.c > +++ b/drivers/gpio/gpio-omap.c > @@ -578,6 +578,7 @@ static void omap_enable_gpio_irqbank(struct gpio_bank *bank, int gpio_mask) > } > > writel_relaxed(l, reg); > + l = readl_relaxed(reg); > } > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
