alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Nobin Mathew <nobin.mathew@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: Power management state flow in ALSA
Date: Fri, 01 Jun 2007 13:18:21 +0100	[thread overview]
Message-ID: <1180700301.26032.50.camel@localhost.localdomain> (raw)
In-Reply-To: <s5hy7j6fuhd.wl%tiwai@suse.de>

Nobin,

Can you try the following patch :-

http://opensource.wolfsonmicro.com/cgi-bin/gitweb/gitweb.cgi?p=linux-2.6-asoc;a=commit;h=6c868238a5e083dca4d74439a7fd467b5c7726b0

This will notify pcm's of their suspend state.

Liam

On Wed, 2007-05-30 at 12:58 +0200, Takashi Iwai wrote:
> At Wed, 30 May 2007 16:06:54 +0530,
> Nobin Mathew wrote:
> > 
> > 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 ?
> 
> I suppose so.
> In soc_suspend() and soc_resume(), you can get the card instance from
> codec->card, at least.
> 
> But currently SoC doesn't keep the PCM instances, so it cannot be
> implemented as it is...  Liam, any plan or known issue regarding this?
> 
> 
> Takashi

  parent reply	other threads:[~2007-06-01 12:18 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
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 [this message]
     [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=1180700301.26032.50.camel@localhost.localdomain \
    --to=lg@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=nobin.mathew@gmail.com \
    --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).