public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: alsa-devel@alsa-project.org
Cc: "ext Aggarwal, Anuj" <anuj.aggarwal@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [alsa-devel] Audio suspend/resume status on OMAP3 based platforms
Date: Wed, 13 Jan 2010 09:10:04 +0200	[thread overview]
Message-ID: <201001130910.04292.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB031E1D7807@dbde02.ent.ti.com>

On Tuesday 12 January 2010 18:05:15 ext Aggarwal, Anuj wrote:
> Hi,
> 
> 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.

As Jarkko pointed out in a separate mail, we should not expect the 
suspend/resume to be working correctly until the context save/restore, and the 
clock management is sorted out.

On the other hand it seams that the problem is in the capture path (b and c 
having issues).

How is the McBSP configured in your setup (master or slave)?
I think we might have different issues with suspend/resume when OMAP McBSP is 
slave or if it is master.

-- 
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-01-13  7:10 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
2010-01-13  7:10 ` Peter Ujfalusi [this message]
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=201001130910.04292.peter.ujfalusi@nokia.com \
    --to=peter.ujfalusi@nokia.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