On Fri, Feb 11, 2011 at 05:37:04PM +0530, Santosh Shilimkar wrote:

There is a Monitor secure API, needs to be called from non-secure
software to set this diagnostic registers in resume path.

It would be an idea to get the OMAP sleep code up to date so that I can
look at OMAPs requirements for this to be useful.

As the current code stands, I don't see any reason why the sleep34xx code
can't use this infrastructure, but I'm loathed to start modifying that if
there's outstanding code changes in that area.