From: Raymond Yau <superquad.vortex2@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: Duplicate wake-ups in pcm_lib.c
Date: Wed, 13 Jan 2010 14:58:41 +0800 [thread overview]
Message-ID: <4f3252891001122258j5c3bd7c5u7184cad199f5cf40@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1001110814310.4210@eeebox2.perex-int.cz>
2010/1/11 Jaroslav Kysela <perex@perex.cz>
> On Mon, 11 Jan 2010, Raymond Yau wrote:
>
> 2010/1/7 Jaroslav Kysela <perex@perex.cz>
>>
>> On Wed, 6 Jan 2010, pl bossart wrote:
>>>
>>>
>>>
>>> The improved and more clean fix in now in my tree:
>>>
>>>
>>>
>>> http://git.alsa-project.org/?p=alsa-kernel.git;a=commitdiff;h=1250932e48d3b698415b1f04775433cf1da688d6
>>>
>>> Note that you should apply these 4 patches (in reverse order):
>>>
>>> 4: ALSA: pcm_lib - optimize wake_up() calls for PCM I/O
>>> 3: ALSA: pcm_lib - cleanup & merge hw_ptr update functions
>>> 2: ALSA: pcm_lib - add possibility to log last 10 DMA ring buffer
>>> positions
>>> 1: ALSA: pcm_lib.c - convert second xrun_debug() parameter to use defines
>>>
>>> Patch #3 should definitely fix problems with large avail or delay values
>>> reported in PA. I finally figured the culprit (and decide to cleanup all
>>> relevant code rather do just another workaround). In other words, new
>>> hw_ptr pointer should never be less than previous one now.
>>>
>>> Jaroslav
>>>
>>> -
>>>
>>>
>> using alsa-driver-1.0.22.1.1.g231e3.14.g812cb and Fedora 12 inside Virtual
>> Box
>>
>> aplay -D plughw:0,0 /usr/share/sounds/alsa/*.wav
>>
>> "Front Left" sound as "Front Front Left" when playing "Front_left.wav"
>>
>> only when echo 4 > /proc/asound/card0/pcm0p/xrun_debug
>>
>
> Thanks for testing.
>
> It means that with other values is no sound generated?
>
> Could you use value 29 for xrun_debug and report all sound related messages
> from dmesg output after playback of "Front_left.wav"?
>
> Jaroslav
>
> -----
do you mean 27 instead of 29 since the echo only occur when the value
contain XRUN_DEBUG_JIFFIESCHECK bit ?
aplay -Dplughw:0,0 and mplayer -ao alsa:device=hw=0,0 work normal
except when the value of xrun_debug contain XRUN_DEBUG_JIFFIESCHECK bit (
same result for the three virtual box audio backend oss, pulseaudio and
alsa )
next prev parent reply other threads:[~2010-01-13 6:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 20:28 Duplicate wake-ups in pcm_lib.c pl bossart
2009-12-24 8:43 ` Jaroslav Kysela
2009-12-25 6:59 ` Raymond Yau
2010-01-07 4:59 ` pl bossart
2010-01-07 14:59 ` Jaroslav Kysela
2010-01-11 4:11 ` Raymond Yau
2010-01-11 7:18 ` Jaroslav Kysela
2010-01-13 6:58 ` Raymond Yau [this message]
2010-01-13 7:20 ` Jaroslav Kysela
2010-01-20 7:38 ` Raymond Yau
2010-01-20 10:42 ` Jaroslav Kysela
2010-01-26 7:25 ` Raymond Yau
2010-01-26 8:23 ` Jaroslav Kysela
2010-01-11 18:36 ` pl bossart
2010-01-11 18:45 ` pl bossart
2010-01-11 18:54 ` Jaroslav Kysela
2010-01-11 18:51 ` Jaroslav Kysela
2010-01-11 20:46 ` pl bossart
2010-01-12 11:15 ` Jaroslav Kysela
2010-01-18 18:32 ` Colin Guthrie
2010-01-18 21:39 ` Jaroslav Kysela
2010-01-20 1:24 ` Colin Guthrie
2010-01-20 15:12 ` Colin Guthrie
2010-01-25 11:52 ` Colin Guthrie
2010-01-27 10:46 ` Colin Guthrie
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=4f3252891001122258j5c3bd7c5u7184cad199f5cf40@mail.gmail.com \
--to=superquad.vortex2@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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).