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: [alsa-devel] Compressed Audio Playback/Capture through ALSA framework
Date: Wed, 16 Mar 2011 18:08:28 +0000 [thread overview]
Message-ID: <20110316180828.GC15605@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTikomFyMpGQMgysHdj8b3i-_jjhwW+7PVK0+HZ-p@mail.gmail.com>
On Wed, Mar 16, 2011 at 01:00:09PM -0500, pl bossart wrote:
> On Wed, Mar 16, 2011 at 12:53 PM, Mark Brown
> > It'd make the tie up with algorithms part much easier as we could have
> > an interface for transferring the compressed data alone and then
> > externally describe how that's plumbed into any other DSP that's going
> > on and the physical outputs - it'd help with treating the data transfer
> > as a standalone problem.
> Still not convinced. Why would you need to 'externally describe' how
> compressed data is linked to post-processing. It's all part of DSP
> firmware, why should anyone care how the decoder provides data to
> post-processes? You can control post-processes with ALSA controls as
> for regular PCM.
The problem is figuring out which controls are where and what can be
joined up with what. This is a problem with regular PCM too but it gets
much worse when everything is virtual. Media controller should provide
a route to allowing applications to figure out what's going on in the
hardware.
next prev parent reply other threads:[~2011-03-16 18:08 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 [this message]
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
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=20110316180828.GC15605@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 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).