> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > owner@xxxxxxxxxxxxxxx] On Behalf Of Kevin Hilman > I'm a little puzzled on this one. My understanding is that the IO pad > is only armed when CORE is in RET or OFF. For ES3 and before the io ring wake was 'armed' when ever core went to idle. When core power state changed accounting was done for state. This scheme created a small time window where per wake events could be lost in handoff from gpio to io daisy chain when targeting chip off. In ES3.1 the EN_IO_CHAIN bit was added as a way to cover this hole. It allows enabling the wake up daisy chain in software prior to idling core. The trm does detail the exact steps. The 3.1 bug fix covered the transition window observed going to chip states but probably can cover here. I'm not sure about the patch as applied with studying. Regards, Richard W. -- 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
