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] ASoC: core - Add support for DAI and machine kcontrols.
Date: Mon, 6 Feb 2012 18:19:38 +0000 [thread overview]
Message-ID: <20120206181938.GA5751@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1328551752.26182.141.camel@vkoul-udesk3>
[-- Attachment #1.1: Type: text/plain, Size: 640 bytes --]
On Mon, Feb 06, 2012 at 11:39:12PM +0530, Vinod Koul wrote:
> On Mon, 2012-02-06 at 15:17 +0000, Mark Brown wrote:
> > Yes, or rather if the machine driver is peering into the CODEC internals
> > at all something went wrong.
> Yes it was wrongly done due to "historical" reasons. We should ideally
> move this to codec driver... Let me see how I can fix this up :)
Looking at the code I'm pretty sure it's the fanout mux thing (I think I
remember discussing it with you) - DAPM supports muxes selecting one of
n inputs for an output but it doesn't support muxes mapping one input to
one of many outputs. Could be something else though.
[-- 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 18:19 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
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 [this message]
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=20120206181938.GA5751@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 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.