From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: pl bossart <bossart.nospam@gmail.com>
Cc: "Koul, Vinod" <vinod.koul@intel.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Patrick Lai <plai@codeaurora.org>,
alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Compressed Audio Playback/Capture through ALSA framework
Date: Tue, 22 Mar 2011 13:01:11 +0000 [thread overview]
Message-ID: <20110322130110.GB22583@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTinOmh1RBgd5g3F59ZwnF7nhR_QJ+LbGN60AkZUO@mail.gmail.com>
On Fri, Mar 18, 2011 at 11:03:57AM -0500, pl bossart wrote:
> I don't disagree, but I view tunneling as very difficult to implement
> when you have something like PulseAudio or AudioFlinger handling all
> the routing, policy and volume control. The approach based on
I don't think it's an intractible problem - I think we can get to a
point where UCM when asked for an output stream hands back either an
object of some type which wraps up a sink and any controls for that sink
has well enough for PulseAudio or AudioFlinger to figure out if it wants
to layer anything on top to provide functionality like per-stream volume
control.
> passthrough makes things simpler in terms of links/routing/policy.
> Instead of tunneling you push compressed data as far as possible into
> the sink. The application doesn't need to know what the connections
> are, this can be handled at the driver/fw level
The application doesn't need this but the audio daemon does so that we
can support multiple output paths depending on the audio type.
next prev parent reply other threads:[~2011-03-22 13:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 18:31 Compressed Audio Playback/Capture through ALSA framework Patrick Lai
2011-03-15 20:40 ` Eliot Blennerhassett
2011-03-15 20:52 ` [alsa-devel] " pl bossart
2011-03-15 23:28 ` Patrick Lai
2011-03-16 7:21 ` [alsa-devel] " Clemens Ladisch
2011-03-16 7:23 ` Jaroslav Kysela
2011-03-16 22:08 ` Patrick Lai
2011-03-17 7:39 ` [alsa-devel] " Clemens Ladisch
2011-03-16 10:38 ` Mark Brown
2011-03-16 10:59 ` Koul, Vinod
2011-03-16 11:56 ` Mark Brown
2011-03-16 12:17 ` Koul, Vinod
2011-03-16 17:52 ` pl bossart
2011-03-16 17:53 ` Mark Brown
2011-03-16 18:00 ` pl bossart
2011-03-16 18:08 ` Mark Brown
2011-03-17 2:21 ` Koul, Vinod
2011-03-17 5:00 ` Patrick Lai
2011-03-17 11:54 ` Mark Brown
2011-03-17 14:27 ` pl bossart
2011-03-17 18:25 ` Mark Brown
2011-03-17 19:16 ` [alsa-devel] " pl bossart
2011-03-17 20:16 ` Mark Brown
2011-03-17 21:19 ` Patrick Lai
2011-03-17 21:25 ` Mark Brown
2011-03-18 16:03 ` pl bossart
2011-03-22 13:01 ` Mark Brown [this message]
2011-03-17 5:32 ` Asus E35M1-M Pro and Realtek AL887-VD - no love from ALSA for Sourround Wojciech Myrda
2011-03-17 21:55 ` Paul Menzel
2011-03-20 10:13 ` Wojciech Myrda
2011-03-18 2:22 ` Compressed Audio Playback/Capture through ALSA framework Raymond Yau
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=20110322130110.GB22583@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=bossart.nospam@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=plai@codeaurora.org \
--cc=vinod.koul@intel.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 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.