From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Nobin Mathew <nobin.mathew@gmail.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org
Subject: Re: [ALSA] ALSA Power Management, Drivers behaving unexpectedly after suspend/resume cycle
Date: Fri, 25 May 2007 14:19:09 +0100 [thread overview]
Message-ID: <1180099149.13652.77.camel@localhost.localdomain> (raw)
In-Reply-To: <8d6898730705250554w31d4a3abr80b8b531f8398642@mail.gmail.com>
On Fri, 2007-05-25 at 18:24 +0530, Nobin Mathew wrote:
> after resume when i do playback i am getting same number of DMA
> interrupt as in the working case (after reboot).
>
So, does aplay keeps playing until the end of your file or does it stop
after a short time due to no periods being transmitted to the codec (io
error) ? If it keeps playing then check the codec driver, it's possible
it hasn't resumed fully.
> I am using aplay (/usr/share/sounds/alsa/Side_Right.wav)
>
> But i am not getting any sound (3 underruns), my codec register
> contents and controller register contents are same.
>
Codec drivers cache registers for faster IO, best make sure the cache is
refreshed at resume.
Also, what happens when you kill aplay and restart it after resume ?
Does audio play or does it still underrun with no audio ? If audio
works, then this suggests something in your resume path is missing.
Fwiw, I would expect to sometimes see an underrun at resume due to
resume being a busy period for most systems.
Liam
next prev parent reply other threads:[~2007-05-25 13:19 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
2007-05-25 12:39 ` Liam Girdwood
2007-05-25 12:54 ` Nobin Mathew
2007-05-25 13:19 ` Liam Girdwood [this message]
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=1180099149.13652.77.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 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.