From: "Nobin Mathew" <nobin.mathew@gmail.com>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de
Subject: Re: [ALSA] ALSA Power Management, Drivers behaving unexpectedly after suspend/resume cycle
Date: Fri, 25 May 2007 17:34:08 +0530 [thread overview]
Message-ID: <8d6898730705250504p442190e6u5bf71fbcd947df38@mail.gmail.com> (raw)
In-Reply-To: <s5h3b1lp75g.wl%tiwai@suse.de>
Every ALSA driver is calling these for suspend
snd_power_change_state(card, SNDRV_CTL_POWER_D3hot);
snd_pcm_suspend_all(pcm[i]);
And for resume
snd_power_change_state(card, SNDRV_CTL_POWER_D0)
In ALSA ASoC no driver is calling any of this, even not in soc-core.c
My driver is an ASoC driver and I am also not calling these functions
Will this cause any Issue?
Thanks
On 5/25/07, Takashi Iwai <tiwai@suse.de> wrote:
> At Fri, 25 May 2007 11:27:10 +0530,
> Nobin Mathew wrote:
> >
> > I am implementing power management in my ALSA sound drivers. ALSA
> > drivers are not working properly after resume. All registers values
> > are proper and I am able to read back the codec register contents.
> >
> > If I do a playback after resume then I am getting lots of "underrun".
>
> As Liam already pointed, the underrun is usually irrelevant from the
> codec registers, as codec chips don't control the DMA transfer.
> So, it's likely a controller side problem.
>
> > After a reboot playback is working fine.
> >
> > Is there any known issues with ALSA power management?
>
> No. Some drivers may have, but no problem in general.
>
> > Why Ubuntu and Redhat does ALSA modules removal before suspend and
> > insertion after resume?
>
> They are either too lazy or too conservative :)
>
>
> Takashi
>
next prev parent reply other threads:[~2007-05-25 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 5:57 [ALSA] ALSA Power Management, Drivers behaving unexpectedly after suspend/resume cycle Nobin Mathew
2007-05-25 9:09 ` Liam Girdwood
2007-05-25 9:46 ` Takashi Iwai
2007-05-25 12:04 ` Nobin Mathew [this message]
2007-05-25 12:39 ` Liam Girdwood
2007-05-25 12:54 ` Nobin Mathew
2007-05-25 13:19 ` Liam Girdwood
2007-05-25 13:23 ` Takashi Iwai
2007-05-28 9:16 ` Nobin Mathew
2007-05-28 10:15 ` Nobin Mathew
2007-05-28 12:39 ` 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=8d6898730705250504p442190e6u5bf71fbcd947df38@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).