From: Clemens Ladisch <clemens@ladisch.de>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: alsa-devel mailing list <alsa-devel@alsa-project.org>
Subject: Re: Implementing sync start
Date: Mon, 10 Aug 2009 13:57:59 +0200 [thread overview]
Message-ID: <4A800B47.6020201@ladisch.de> (raw)
In-Reply-To: <9e4733910908100445u3ea02395y9dc39b73ad41cb6b@mail.gmail.com>
Jon Smirl wrote:
> On Mon, Aug 10, 2009 at 3:40 AM, Clemens Ladisch<clemens@ladisch.de> wrote:
>> There is no common code for the two substreams.
>> Is your hardware actually capable of starting them at exactly the same
>> time?
>
> Sync start is working. This is in the loop and starts the streams:
> bcom_enable(s->bcom_task);
> s is set to two different values in the loop.
But you are calling bcom_enable() twice, once for each stream. The same
would happen if you didn't implement sync start and let ALSA handle the
linked streams.
Sync start/stop is intended for hardware that can actually start two
streams at _exactly_ the same time, by, e.g., writing a value with two
bits set to a register.
> I'm having problems with the drain error on stop.
> ALSA sound/core/pcm_native.c:1499: playback drain error (DMA or IRQ trouble?)
ALSA did not get the snd_pcm_period_elapsed() call (or the correct
pointer value) for the last samples.
HTH
Clemens
next prev parent reply other threads:[~2009-08-10 11:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 18:16 Implementing sync start Jon Smirl
2009-08-09 3:07 ` Jon Smirl
2009-08-10 2:13 ` Jon Smirl
2009-08-10 2:19 ` Jon Smirl
2009-08-10 7:40 ` Clemens Ladisch
2009-08-10 11:45 ` Jon Smirl
2009-08-10 11:57 ` Clemens Ladisch [this message]
2009-08-10 12:24 ` Jon Smirl
2009-08-10 12:29 ` Clemens Ladisch
2009-08-10 12:41 ` Jon Smirl
2009-08-10 12:43 ` Mark Brown
2009-08-10 12:46 ` Jon Smirl
2009-08-10 13:30 ` Clemens Ladisch
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=4A800B47.6020201@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=jonsmirl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox