Hi Tony,
On 07/18/2013 12:04 PM, Tony Lindgren wrote:
* Grygorii Strashko <grygorii.strashko@xxxxxx> [130718 02:01]:
On 07/18/2013 11:09 AM, Tony Lindgren wrote:
Don't think it's debug code - IO chain need to be rearmed after each
PRCM IO IRQ - otherwise IO wakeup events may be lost (at least on
OMAP4, OMAP5 requires more complex handling(( ).
Nope, only after the mux register changes. I've verified it on
am3730 with off-idle for both serial and wl12xx.
Unfortunately, there is a possibility to lose wake up events in case if
IO daisy chain will be rearmed (this will clean up all WAKEUPEVENT bits)
while there is some pending WAKEUP event present. In this case,
pcs_omap_handle_irq() will not call generic_handle_irq(wakeirq).
The below patch contains explanation of such kind of issue we've solved
in K3.4
http://git.omapzoom.org/?p=kernel/omap.git;a=commit;h=5ff316db224a2c3c23bfe44261275d520b4f78bb
Currently, in Mainline the same is possible on OMAP4 (which is SMP) if
some Device will be switched to idle and rearm IO chain while there is
pending WAKEUP event form USB for example. So, IO rearming need to be
delayed until PRCM irq will be served served and PRCM irq handler should
finally rearm IO daisy chain.
I didn't pick up your padconf patches yet -seems i need to be in sync :)
Well you need those for proper wake-up event support..
Below the diff I used to verify IO wake up (It follows old IO daisy
chain hanlding models in hwmod before DT):
..then these changes not needed with the pinctrl-single changes.
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
