From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 1/2] ASoC: core - Add direct mapping between DAIs and DAPM
Date: Thu, 16 Feb 2012 21:43:40 -0800 [thread overview]
Message-ID: <20120217054339.GB1231@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1329457253.24656.7.camel@vkoul-udesk3>
[-- Attachment #1.1: Type: text/plain, Size: 937 bytes --]
On Fri, Feb 17, 2012 at 11:10:53AM +0530, Vinod Koul wrote:
> On Thu, 2012-02-16 at 09:59 -0800, Mark Brown wrote:
> > We actually need to do that anyway for the CODEC<->CODEC links, I've got
> > use cases where there are multiple independant streams going over the
> > same DAI on different channels (eg, stereo pair on 0 and 1, another
> > stereo pair on 2 and 3).
> Is this a TDM DAI you are referring to?
They can be, they can also be grouped together to make multi-channel
links. It's entirely flexible to software on the devices I'm thinking
of.
> > I *think* can get something working quickly that doesn't fill in the
> > blanks for CODEC-CODEC links, though the conference is looking quite
> > interesting today. I'll try to send something later.
> On conference, when are we planing our next ASoC conference?
Not at present. It would probably have been colocated with ELC but
that didn't happen.
[-- 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-02-17 5:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 16:02 [PATCH 1/2] ASoC: core - Add direct mapping between DAIs and DAPM Liam Girdwood
2012-02-15 16:02 ` [PATCH 2/2] ASoC: core - Add support for direct DAI -> widget mapping stream events Liam Girdwood
2012-02-15 16:24 ` [PATCH 1/2] ASoC: core - Add direct mapping between DAIs and DAPM Mark Brown
2012-02-16 13:35 ` Liam Girdwood
2012-02-16 17:59 ` Mark Brown
2012-02-17 5:40 ` Vinod Koul
2012-02-17 5:43 ` Mark Brown [this message]
2012-02-17 10:47 ` 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=20120217054339.GB1231@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=vinod.koul@linux.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).