From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Nobin Mathew <nobin.mathew@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [ALSA] ALSA Power Management, Drivers behaving unexpectedly after suspend/resume cycle
Date: Fri, 25 May 2007 10:09:28 +0100 [thread overview]
Message-ID: <1180084168.13652.11.camel@localhost.localdomain> (raw)
In-Reply-To: <8d6898730705242257k6da2088fi80f0d4034ed78986@mail.gmail.com>
On Fri, 2007-05-25 at 11:27 +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.
>
Iirc, you are using an AC97 codec. This means that the AC97 link is
running as expected after resume.
> If I do a playback after resume then I am getting lots of "underrun".
>
Do you hear any audio at all ? The underruns are probably being caused
by the AC97 Tx FIFO not being filled quickly enough by DMA. Is your DMA
being set up correctly after resume ?
>
> After a reboot playback is working fine.
>
> Is there any known issues with ALSA power management?
ALSA suspend and resume works fine on lots of devices (all the ones I
have). I suspect you have a driver problem.
Liam
next prev parent reply other threads:[~2007-05-25 9:09 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 [this message]
2007-05-25 9:46 ` Takashi Iwai
2007-05-25 12:04 ` Nobin Mathew
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=1180084168.13652.11.camel@localhost.localdomain \
--to=lg@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=nobin.mathew@gmail.com \
/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.