Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: core - PCM mutex per rtd
Date: Thu, 9 Jun 2011 20:06:25 +0100	[thread overview]
Message-ID: <20110609190624.GA2821@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1307635479-3586-1-git-send-email-lrg@ti.com>

On Thu, Jun 09, 2011 at 05:04:39PM +0100, Liam Girdwood wrote:
> In preparation for the new ASoC Dynamic PCM support (AKA DSP support).
> 
> The new ASoC Dynamic PCM core allows DAIs to be dynamically re-routed
> at runtime between the PCM device end (or Frontend - FE) and the physical DAI
> (Backend - BE) using regular kcontrols (just like a hardware CODEC routes
> audio in the analog domain). The Dynamic PCM core therefore must be
> able to call PCM operations for both the Frontend and Backend(s) DAIs at
> the same time.

Applied, thanks.

      reply	other threads:[~2011-06-09 19:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 16:04 [PATCH] ASoC: core - PCM mutex per rtd Liam Girdwood
2011-06-09 19:06 ` Mark Brown [this message]

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=20110609190624.GA2821@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@ti.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