From: Jarkko Nikula <jhnikula@gmail.com>
To: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Audio suspend/resume status on OMAP3 based platforms
Date: Wed, 13 Jan 2010 08:58:20 +0200 [thread overview]
Message-ID: <20100113085820.6d8564d4.jhnikula@gmail.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB031E1D7807@dbde02.ent.ti.com>
On Tue, 12 Jan 2010 21:35:15 +0530
"Aggarwal, Anuj" <anuj.aggarwal@ti.com> wrote:
> I want to check the status of suspend/resume functionality when audio
> subsystem is being used. Specifically, has some one tried the following
> tests on their omap3 based platforms:
>
> a) echo mem > /sys/power/state, when audio playback is running in
> background
> b) same command, when audio capture is running in
> background
> b) same command, when audio loopback is running in
> background
>
> I am facing some issues with (b) & (c) so wanted to confirm whether
> someone else has faced similar problem or not.
>
Unfortunately the proper OMAP ASoC suspend/resume functionality is still
missing and the development progress has been slow. There are few
issues in low-level McBSP code like proper clock management,
context save/restore, how to deal with the FIFO, etc. and those should
be addressed first.
Fortunately Janusz Krzysztofik has been cleaning up and developing the
register cache support in McBSP and that work could help the PM work as
well. Clock management changes don't look complicated but just requires
that one develops it.
http://mailman.alsa-project.org/pipermail/alsa-devel/2009-November/023119.html
--
Jarkko
next prev parent reply other threads:[~2010-01-13 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 16:05 Audio suspend/resume status on OMAP3 based platforms Aggarwal, Anuj
2010-01-12 16:11 ` [alsa-devel] " Mark Brown
2010-01-12 17:49 ` Anuj Aggarwal
2010-01-13 6:58 ` Jarkko Nikula [this message]
2010-01-13 7:10 ` Peter Ujfalusi
2010-01-13 8:52 ` Aggarwal, Anuj
2010-01-15 18:00 ` Aggarwal, Anuj
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=20100113085820.6d8564d4.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=linux-omap@vger.kernel.org \
/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