"Nayak, Rajendra" <[email protected]> writes: >From: Högander Jouni [mailto:[email protected]] >> >>ext Rajendra Nayak <[email protected]> writes: >> >>> There is a design requirement in OMAP3 that Auto_RET and AUTO_OFF >>> should not be set together. The PRCM FSM has been coded assuming >>> that SW will set either auto_ret or auto_off bit depending on >>> whether the core has been programmed to go into open switched >>> logic retention state or OFF state. They are mutually exclusive. >> >>So we don't have to do this if closed switch retention is used? (This >>is what is currently used in linux-omap:pm) > > Currently in the pm branch AUTO_RET is enabled at init and kept > enabled. While attempting a OFF state AUTO_OFF is enabled also > leaving AUTO_RET and AUTO_OFF both enabled.
A little more clarification needed, in particular whether or how this affects closed-switch retention. The description above states that this problem affects OSWR and OFF. linux-omap PM only uses CSWR, so based on the description of the PRCM FSM above, for CSWR, we should never be setting AUTO_RET when using CSWR. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
