* Ladislav Michl <ladis@xxxxxxxxxxxxxx> [171015 15:16]: > On Sun, Oct 15, 2017 at 09:22:31AM -0700, Tony Lindgren wrote: > > * Reizer, Eyal <eyalr@xxxxxx> [171014 23:55]: > > > > From: Tony Lindgren [mailto:tony@xxxxxxxxxxx] > > > > > > > > On omaps, if the wlcore interrupt is configured as level instead of edge, > > > > L4PER will stop doing hardware based idling after ifconfig wlan0 down is > > > > done and the WL_EN line is pulled down. > > > > > > > Do we understand why omap is doing this? Is it a bug or a normal behavior? > > > > > > AFAIK way back edge interrupts have been used. On some omaps based boards. > > > They have used level interrupts instead due to occasional interrupts being missed > > > By the omap interrupts controller when using edge based interrupts which caused > > > Issues. This was the reason many boards are set to using level based interrupts which > > > Seemed much more robust. > > > > No idea yet why exactly the gpio modules won't idle after that. But for making > > edge interrupts behave, I suspect that Grygorii's patch "[RESEND PATCH] gpio: > > omap: Fix lost edge interrupts" fixes those issues. > > Please note, that Grygorii's patch fixes occasional edge interrupts misses > only after your PM patch is applied. That said, edge interrupts are still > being missed in mainline. I think that's for omap2 and 3 based boards. Sounds like we may have a generic test case here on omap3 for that issue. I'll do some ping tests against wl12xx on omap3-evm today while it's idling. Regards, Tony -- 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
