[PATCH 15/15] ARM: OMAP2+: AM33XX: Basic suspend resume support
vaibhav.bedia at ti.com
Wed Nov 7 08:25:56 EST 2012
On Wed, Nov 07, 2012 at 06:36:06, Kevin Hilman wrote:
> "Bedia, Vaibhav" <vaibhav.bedia at ti.com> writes:
> > On Mon, Nov 05, 2012 at 23:10:27, Kevin Hilman wrote:
> >> Also, if there are drivers for these devices, won't this interfere?
> > Hmm, I can think of the following scenarios
> > 1. Runtime PM adapted drivers are compiled in - We'll have to ensure that
> > in their suspend callbacks they end up doing omap_hwmod_idle() via the
> > runtime PM APIs.
> That already happens for all omap_devices.
> > In this case the omap_hwmod_enable() followed by omap_hwmod_idle() is
> > not necessary in the PM code.
> > 2. The drivers are not compiled in - In this case, the hwmod code puts
> > the IPs in standby during bootup so the first suspend-resume iteration
> > will pass. During resuming, the SYSC configuration for forced standby will
> > be lost,
> Please clarify how the SYSC is lost in this case.
The register configuration of IPs in the PER domain is lost when we enter
the suspend state. So the forced standby configuration from SYSC is lost
and we need to do this for every successful suspend-resume cycle.
> > so in the subsequent iterations these IPs won't go standby and the
> > hwmod code does not touch them since they never got enabled. In this case
> > we do need the sequence that is there currently.
> > 3. For some reason the respective drivers don't idle the IPs during suspend -
> > (no_idle_on_suspend flag for the hwmod in DT?). In this scenario I think
> > we should abort the suspend process since we know that the suspend is not
> > going to work.
> > Is there some other scenario that needs to be covered?
> You covered the ones I was thinking of.
> > How about adding some flag in hwmod code for handling this? Something
> > similar to what was done for MMC . I think the problem that we have
> > is in some ways similar to the one addressed in .
> Except that in the absence of drivers, no hwmod code is executed on the
> suspend/resume path.
We could perhaps add a couple of APIs to check the SYSC values when coming
out of suspend and take appropriate action if the sysc cache does not match?
More information about the linux-arm-kernel