From: pl bossart <bossart.nospam@gmail.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Lennart Poettering <lennart@poettering.net>
Subject: Re: Duplicate wake-ups in pcm_lib.c
Date: Mon, 11 Jan 2010 14:46:33 -0600 [thread overview]
Message-ID: <6160a5131001111246m48448cedrfa83f9ae39cd6403@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1001111949180.4210@eeebox2.perex-int.cz>
>> I couldn't figure out who generates this null event, and even better
>> it does not show in the report printed by my test app. I am somewhat
>> lost here as to how snd_pcm_playback_poll works.
>
> Note that do_poll() in linux/fs/select.c first checks all given fds
> if there's an event. So probably the userspace just called poll() for a
> reason in different timing than sound one (processing event from another fd
> or so). I believe it's normal behaviour.
This was tested with alsa-lib/test/pcm.c; there's only one call to
poll() with a -1 timeout value. What I fail to understand is why I see
this null event in pcm_native.c, and nothing reported in userspace by
the wait_for_poll() loop in alsa-lib/test/pcm.c
next prev parent reply other threads:[~2010-01-11 20:46 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
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 [this message]
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=6160a5131001111246m48448cedrfa83f9ae39cd6403@mail.gmail.com \
--to=bossart.nospam@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=lennart@poettering.net \
--cc=perex@perex.cz \
/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).