From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Giuliano Pochini <pochini@shiny.it>, alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] Kernel crash
Date: Fri, 17 Sep 2004 12:32:44 +0200 [thread overview]
Message-ID: <s5hu0tx18z7.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5hvfed19gw.wl@alsa2.suse.de>
At Fri, 17 Sep 2004 12:22:07 +0200,
I wrote:
>
> > The linking makes sense for hardware that support that. Otherwise, we can
> > start streams in most close time, but draining and dropping doesn't make
> > much sense, because different clocking sources for different cards will
> > produce jitter, thus there is no real sync and application must care.
>
> Agreed. I've assumed that drain/drop are supposed to be synchronous,
> but they should not.
I just noticed that pcm_multi.c _assumes_ indeed that linked
draining/dropping works as synchronized. So, the current semantics is
correct.
If snd_pcm_drain() affects only the given stream, then it's difficult
to get sync among all streams, because basically draining consists of
two phases:
- trigger DRAIN state to all streams
- wait until all streams get drained
We cannot do the procedure above in the serialized manner.
Also, another question is how to handle XRUN state.
When one of the linked streams gets XRUN, should all streams be
stopped and marked as XRUN? I think yes.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
next prev parent reply other threads:[~2004-09-17 10:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 18:51 Kernel crash Giuliano Pochini
2004-09-06 15:16 ` Takashi Iwai
2004-09-07 7:55 ` Giuliano Pochini
2004-09-11 19:02 ` [PATCH] " Giuliano Pochini
2004-09-13 15:00 ` Takashi Iwai
2004-09-13 20:07 ` Giuliano Pochini
2004-09-15 10:24 ` Takashi Iwai
2004-09-15 17:50 ` Giuliano Pochini
2004-09-15 18:01 ` Takashi Iwai
2004-09-16 11:16 ` Takashi Iwai
2004-09-16 19:56 ` Giuliano Pochini
2004-09-17 6:54 ` Jaroslav Kysela
2004-09-17 10:22 ` Takashi Iwai
2004-09-17 10:32 ` Takashi Iwai [this message]
2004-09-22 8:08 ` Jaroslav Kysela
2004-09-22 10:08 ` Takashi Iwai
2004-09-22 14:12 ` Giuliano Pochini
2004-09-23 7:43 ` Jaroslav Kysela
2004-09-24 13:30 ` Takashi Iwai
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=s5hu0tx18z7.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
--cc=pochini@shiny.it \
/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.