From: Patrick Lai <plai@codeaurora.org>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmciro.com>
Subject: Re: Playback and capture synchronization
Date: Wed, 09 Nov 2011 10:38:05 -0800 [thread overview]
Message-ID: <4EBAC88D.1040508@codeaurora.org> (raw)
In-Reply-To: <4EBA6A22.6090308@ladisch.de>
On 11/9/2011 3:55 AM, Clemens Ladisch wrote:
> Patrick Lai wrote:
>> I have a use case requiring playback and capture starting at the same
>> time. Latency between starting of playback and capture streams need to
>> be less than few PCM samples. Base on my understanding on ALSA which
>> does not have the concept of grouping multiple streams,
>
> snd_pcm_link()
Awesome! I will look into this API
> If the driver doesn't actually implement starting of linked streams
> (which would be pointless if the hardware doesn't support it), ALSA
> calls the second trigger callback after the first one.
>
> It might be possible to implement simultaneous starting of two streams.
> What hardware (driver) are you using?
It's Qualcomm hardware. As far as I know, HW has this synchronization
support but I would have to build driver to make use of this functionality
Thanks very much for the feedback
>
>
> Regards,
> Clemens
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-11-09 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 2:19 Playback and capture synchronization Patrick Lai
2011-11-09 11:55 ` Clemens Ladisch
2011-11-09 18:38 ` Patrick Lai [this message]
2011-11-09 22:36 ` Eliot Blennerhassett
[not found] <mailman.1622.1320881582.2097.alsa-devel@alsa-project.org>
2011-11-10 14:57 ` anish kumar
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=4EBAC88D.1040508@codeaurora.org \
--to=plai@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmciro.com \
--cc=clemens@ladisch.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.