From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Grazvydas Ignotas <notasas@gmail.com>, lrg@ti.com
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
Kevin Hilman <khilman@ti.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@bitmer.com>
Subject: Re: ASoC related suspend problems on OMAP3
Date: Wed, 8 Feb 2012 11:51:32 +0000 [thread overview]
Message-ID: <20120208115132.GA25756@sirena.org.uk> (raw)
In-Reply-To: <CANOLnOMhetqt0ZCCfS0UwnfE0DxLhLhK9=7t0BaQ1SUsv0OWjw@mail.gmail.com>
On Wed, Feb 08, 2012 at 02:34:38AM +0200, Grazvydas Ignotas wrote:
> Hi,
>
> On OMAP3 pandora, system suspend stops working properly after using
> audio at least once:
Also adding Liam to the CC list (and not deleting any context for
visibility).
>
> (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?
>
> --
> Gra??vydas
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
next prev parent reply other threads:[~2012-02-08 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 0:34 ASoC related suspend problems on OMAP3 Grazvydas Ignotas
2012-02-08 6:59 ` Jarkko Nikula
2012-02-08 8:29 ` Peter Ujfalusi
2012-02-08 11:51 ` Mark Brown [this message]
2012-02-08 16:19 ` [alsa-devel] " Grazvydas Ignotas
2012-02-09 8:59 ` Peter Ujfalusi
2012-02-09 13:41 ` Grazvydas Ignotas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120208115132.GA25756@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jarkko.nikula@bitmer.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=notasas@gmail.com \
--cc=peter.ujfalusi@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).