All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajeev kumar <rajeev-dlh.kumar@st.com>
To: broonie@opensource.wolfsonmicro.com
Cc: alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: Audio:suspend to ram issue
Date: Thu, 18 Aug 2011 16:21:37 +0530	[thread overview]
Message-ID: <4E4CEEB9.2000604@st.com> (raw)
In-Reply-To: <4E4CABBC.20901@st.com>

Hello Mark
In the continuation of the last mail.I run alsa_aplay and the WAV file 
sounds.
Then press ctrl-z - aplay will go to background(suspend state) and i2s 
is stopped.
Then type fg and the audio  restart.
Is there any difference between these two suspend  ctrl-z and echo mem > 
/sys/power/state.
In both the cases trigger will call with cmd value '1 ' in case of 
resume and '0' in case of suspend.

While going through the alsa framework I found that suspend and resume 
functionality is handled by
the framework itself.Please correct me if my understanding is not correct.

Best Regards
Rajeev


On 8/18/2011 11:35 AM, Rajeev kumar wrote:
>
> Hi Mark
> I am not sure about the behavior in case of audio suspend/resume.
>
> I tested the audio driver with aplay and then suspended to ram (using 
> echo mem > /sys/power/state). After pressing wake to resume,
> the audio does not play unless aplay is closed and re-run.  Do we 
> expect the audio suspend/resume to work?
>
> In the platform trigger part I am doing nothing and in case of 
> cpu(i2s) , just disabling the i2s.
>
> Best Regards
> Rajeev

  reply	other threads:[~2011-08-18 10:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18  6:05 Audio:suspend to ram issue Rajeev kumar
2011-08-18 10:51 ` Rajeev kumar [this message]
2011-08-18 16:25   ` Mark Brown
2011-08-19  4:23     ` Rajeev kumar
2011-08-19  8:21       ` Mark Brown
2011-08-18 16:22 ` Mark Brown

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=4E4CEEB9.2000604@st.com \
    --to=rajeev-dlh.kumar@st.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.