From: Liam Girdwood <lrg@ti.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 6/8] ASoC: dapm: Implement and instantiate DAI widgets
Date: Fri, 17 Feb 2012 10:39:18 +0000 [thread overview]
Message-ID: <1329475158.3972.15.camel@odin> (raw)
In-Reply-To: <1329468009.24656.15.camel@vkoul-udesk3>
On Fri, 2012-02-17 at 14:10 +0530, Vinod Koul wrote:
>
> Also in dai widget would it make sense to add channel map and associate
> that with DAI?
>
Yeah, I think that would work. I've already started some work on the
channel mapping (just associating unique PCM channel masks with DAI
widgets) but I do need to upstream dynamic PCM first !
Liam
next prev parent reply other threads:[~2012-02-17 10:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 5:56 [PATCH 1/8] ALSA: core: Constify the name in new kcontrols Mark Brown
2012-02-17 5:56 ` [PATCH 2/8] ASoC: dapm: Unexport snd_soc_dapm_new_control() Mark Brown
2012-02-17 5:56 ` [PATCH 3/8] ASoC: dapm: Refactor snd_soc_dapm_new_widget() to return the widget Mark Brown
2012-02-17 5:56 ` [PATCH 4/8] ASoC: dapm: Supply the DAI and substream when calling stream events Mark Brown
2012-02-17 5:56 ` [PATCH 5/8] ASoC: dapm: Constify lots of names that are never modified Mark Brown
2012-02-17 5:56 ` [PATCH 6/8] ASoC: dapm: Implement and instantiate DAI widgets Mark Brown
2012-02-17 8:40 ` Vinod Koul
2012-02-17 10:39 ` Liam Girdwood [this message]
2012-02-22 12:35 ` Vinod Koul
2012-02-22 12:43 ` Mark Brown
2012-02-22 13:01 ` Vinod Koul
2012-02-22 13:29 ` Mark Brown
2012-02-23 6:50 ` Vinod Koul
2012-02-23 15:25 ` Mark Brown
2012-02-17 5:56 ` [PATCH 7/8] ASoC: dapm: Convert stream events to use " Mark Brown
2012-02-17 5:56 ` [PATCH 8/8] ASoC: wm8994: Convert to use DAI widget routing rather than streams Mark Brown
2012-02-17 9:50 ` [PATCH 1/8] ALSA: core: Constify the name in new kcontrols 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=1329475158.3972.15.camel@odin \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=patches@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.