alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: Patrick Lai <plai@codeaurora.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] Compressed Audio Playback/Capture through ALSA framework
Date: Wed, 16 Mar 2011 11:56:27 +0000	[thread overview]
Message-ID: <20110316115627.GC14125@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1300273162.9428.10.camel@vkoul-udesk3>

On Wed, Mar 16, 2011 at 04:29:22PM +0530, Koul, Vinod wrote:
> On Wed, 2011-03-16 at 16:08 +0530, Mark Brown wrote:

> > Nobody's really tried to do more yet but this may end up being the best
> > choice overall as there's substantial variation in how the DSPs are
> > structured both physically and OS wise which make the abstractions below
> > the userspace API level less clear.

> I was thinking more on having a generic framework which coexists with
> alsa, asoc (dapm), and provided a way to write driver for your dsp to do
> decoder, sink + decoder and other variations.
> The implementation of these can be specific to DSP in question, but
> framework should be able to push and pull data, timing information
> around with a standard way which coexists with current frameworks 

It would be nice to have a standard userspace API for this but I'm not
aware of anyone who's looked at it in detail and you start having to
also take into account other algorithms that are running on the device
so there's nothing to point people at right now and no real prospect of
there being.  I don't know if it's something we can resolve entirely in
the kernel as I'm aware that some of the DSP implementations have
non-trivial management code in userspace that they talk to which may
mean that the standard API has to be a userspace one.  There's also the
difference between memory to memory implementations (which fit into a
userspace chain much more readily) and tunneled implementations (which
do need new infrastructure).

I think this'll get substantially easier to look at once the media
controller API is merged and starts to be used in the audio subsystem.

  reply	other threads:[~2011-03-16 11:56 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 [this message]
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
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=20110316115627.GC14125@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --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).