From: "Nobin Mathew" <nobin.mathew@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Power management state flow in ALSA
Date: Wed, 30 May 2007 16:06:54 +0530 [thread overview]
Message-ID: <8d6898730705300336l4db252e6pa4b7b257de4ed6eb@mail.gmail.com> (raw)
In-Reply-To: <s5h4pluhajo.wl%tiwai@suse.de>
Sorry for my blunders.
driver resume () is not calling snd_pcm_resume().
Suspend only calls snd_pcm_suspend ().
I am writing an ASoC driver, where i can place these calls
snd_power_change_state(card, SNDRV_CTL_POWER_D3hot);
snd_pcm_suspend_all(chip->pcm[i]);
and snd_power_change_state(card, SNDRV_CTL_POWER_D0);
In soc-core.c ?
On 5/30/07, Takashi Iwai <tiwai@suse.de> wrote:
> At Wed, 30 May 2007 15:36:33 +0530,
> Nobin Mathew wrote:
> >
> > In suspend () the application is dead (freezed state) before ALSA
> > driver suspend() is called, so in this there is no way application
> > will get to know the SUSPENDED state of driver.
> >
> >
> > In resume () ALSA driver resume () (changes the state of driver) is
> > called first and then applications are activated.
> >
> > So how the application will get to know the SUSPENDED state of driver
> > through syscall.No syscall () from ALSA apps(freezed) is happening
> > during the SUSPENDED duration of ALSA driver.
>
> Your app shall issue syscalls sooner or later, otherwise you'll have
> no I/O :)
>
> The concept of the (PCM) resume in ALSA is a passive way. The driver
> does _NOT_ resume streams by itself. It waits until the app requests
> to resume. This is designed so because usually the hardware cannot be
> recovered in 100% identical state as before, and often the app needs
> to reset something for the proper restart.
>
> So, when resume callback is executed and the whole kernel PM thing is
> finished, the user-process restarts again. Then it issues syscalls,
> and gets to know to know that the stream is in the suspended state.
> Now it calls alsa-lib snd_pcm_resume() function which issues RESUME
> ioctl to restart.
>
>
> Takashi
>
> >
> >
> >
> > On 5/30/07, Takashi Iwai <tiwai@suse.de> wrote:
> > > At Wed, 30 May 2007 11:52:31 +0530,
> > > Nobin Mathew wrote:
> > > >
> > > > I am having a doubt regarding ALSA power management.
> > > >
> > > > My understanding of APM suspend() is like this.
> > > >
> > > > Freeze the ALSA apps
> > > >
> > > > Call ALSA driver suspend ()
> > > >
> > > > in the ALSA suspend() function it saves the current state of substream
> > > > and changes the state of substream to SUSPENDED.
> > > >
> > > > My understanding of APM resume() is like this
> > > >
> > > > Call ALSA driver resume ()
> > > >
> > > > Activate the ALSA apps
> > > >
> > > > In ALSA resume function it restores the saved state of substream.
> > > >
> > > >
> > > > So my question is when ALSA app will get to know the SUSPENDED state
> > > > of substream.???
> > >
> > > When issuing any syscalls. Then you'll get ESTRPIPE error, which
> > > indicitaes the stream is in the SUSPEND state.
> > >
> > >
> > > Takashi
> > >
> >
>
next prev parent reply other threads:[~2007-05-30 10:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 6:22 Power management state flow in ALSA Nobin Mathew
2007-05-30 9:55 ` Takashi Iwai
2007-05-30 10:06 ` Nobin Mathew
2007-05-30 10:26 ` Takashi Iwai
2007-05-30 10:36 ` Nobin Mathew [this message]
2007-05-30 10:39 ` Takashi Iwai
2007-05-30 10:46 ` Nobin Mathew
2007-05-30 10:58 ` Takashi Iwai
2007-05-30 11:10 ` Liam Girdwood
2007-06-01 12:18 ` Liam Girdwood
[not found] ` <8d6898730706032158i341b70d3j32c9566532395d18@mail.gmail.com>
2007-06-06 8:07 ` Nobin Mathew
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=8d6898730705300336l4db252e6pa4b7b257de4ed6eb@mail.gmail.com \
--to=nobin.mathew@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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).