From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: core - Add support for DAI and machine kcontrols.
Date: Mon, 6 Feb 2012 11:09:40 +0000 [thread overview]
Message-ID: <20120206110939.GC3070@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1328524623.6799.9.camel@odin>
[-- Attachment #1.1: Type: text/plain, Size: 513 bytes --]
On Mon, Feb 06, 2012 at 10:37:03AM +0000, Liam Girdwood wrote:
> On Fri, 2012-02-03 at 20:46 +0000, Mark Brown wrote:
> > to hand but what are the cases where there is CODEC control? This
> > sounds suspicous, perhaps we need some of the drivers enhancing (though
> > no reason to block this patch).
> The other machine drivers were all using the codec pointer to do extra
> codec configuration with their kcontrol code so there was no update for
> them.
Which ones were those? That sounds very suspicous...
[-- 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-06 11:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 17:43 [PATCH] ASoC: core - Add support for DAI and machine kcontrols Liam Girdwood
2012-02-03 20:46 ` Mark Brown
2012-02-06 10:37 ` Liam Girdwood
2012-02-06 11:09 ` Mark Brown [this message]
2012-02-06 12:25 ` Liam Girdwood
2012-02-06 13:27 ` Mark Brown
2012-02-06 14:16 ` Liam Girdwood
2012-02-06 14:26 ` Mark Brown
2012-02-06 15:11 ` Vinod Koul
2012-02-06 15:17 ` Mark Brown
2012-02-06 18:09 ` Vinod Koul
2012-02-06 18:19 ` Mark Brown
2012-02-04 12:42 ` Mark Brown
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=20120206110939.GC3070@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).