On 02/08/2012 02:34 AM, Grazvydas Ignotas wrote: > Hi, > > On OMAP3 pandora, system suspend stops working properly after using > audio at least once: > > (just after boot): > # echo mem > /sys/power/state > [ 12.578186] PM: Entering mem sleep > [ 12.678802] PM: suspend of devices complete after 92.834 msecs > [ 12.688201] PM: late suspend of devices complete after 3.173 msecs > [ 17.607971] Successfully put all powerdomains to target state > > # aplay /dev/zero > ^C > # echo mem > /sys/power/state > [ 104.404663] PM: suspend of devices complete after 78.794 msecs > [ 104.413909] PM: late suspend of devices complete after 3.021 msecs > [ 106.601196] Powerdomain (per_pwrdm) didn't enter target state 1 > [ 106.607421] Powerdomain (core_pwrdm) didn't enter target state 1 > [ 106.613739] Could not enter target state in pm_suspend > > I'm seeing this on 3.2, unable to verify on current Linus HEAD as > something else is preventing core/per low power states there. > Any ideas what could be causing this? Perhaps some clock is left enabled? > If this is still working in 3.1 then one possible reason could be my mcbsp changes between commits 40246e..7bc0c4 that went to 3.2. Unfortunately I'm not near my OMAP3 boards in coming days so I cannot bisect myself. -- Jarkko -- 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
