From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/5] ASoC: dpcm: Add Dynamic PCM core operations.
Date: Thu, 26 Apr 2012 17:54:59 +0100 [thread overview]
Message-ID: <20120426165459.GN3207@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1335352373-5237-1-git-send-email-lrg@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 713 bytes --]
On Wed, Apr 25, 2012 at 12:12:49PM +0100, Liam Girdwood wrote:
> The Dynamic PCM core allows digital audio data to be dynamically
> routed between different ALSA PCMs and DAI links on SoC CPUs with
> on chip DSP devices. e.g. audio data could be played on pcm:0,0 and
> routed to any (or all) SoC DAI links.
I've applied all these now - after recovering from the shock of seeing
them! :)
I think we need to have a look at/think about the no_pcm flag, partly
just in relation to the CODEC<->CODEC code as that's also figuring out
that there's no PCM but it does it just by checking that there's no DMA
driver specified. But I'm not sure what the best thing to do is here
without seeing a machine driver or two.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-04-26 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 11:12 [PATCH 1/5] ASoC: dpcm: Add Dynamic PCM core operations Liam Girdwood
2012-04-25 11:12 ` [PATCH 2/5] ASoC: dpcm: Add debugFS support for DPCM Liam Girdwood
2012-04-26 16:44 ` Mark Brown
2012-04-26 16:57 ` Liam Girdwood
2012-04-25 11:12 ` [PATCH 3/5] ASoC: dpcm: Add runtime dynamic route update Liam Girdwood
2012-04-25 11:12 ` [PATCH 4/5] ASoC: dpcm: Add bespoke trigger() Liam Girdwood
2012-04-25 11:12 ` [PATCH 5/5] ASoC: dpcm: Add API for DAI link substream and runtime lookup Liam Girdwood
2012-04-26 16:54 ` Mark Brown [this message]
2012-04-26 17:04 ` [PATCH 1/5] ASoC: dpcm: Add Dynamic PCM core operations Liam Girdwood
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=20120426165459.GN3207@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;
as well as URLs for NNTP newsgroup(s).