[alsa-devel] [RFC] ASoC: multi-component: Add optional kcontrol prefix name for a DAI link

Liam Girdwood lrg at slimlogic.co.uk
Fri Sep 3 12:00:57 CEST 2010

On Fri, 2010-09-03 at 10:33 +0100, Mark Brown wrote:
> On Fri, Sep 03, 2010 at 10:55:32AM +0300, Jarkko Nikula wrote:
> > So we need to split these into three separate problems:
> > - Prefixing
> > - DAPM linking between codecs
> > - Registering DAIless codecs in machine drivers
> > What you think: is it better to hold my prefixing patch until DAPM
> > linking is solved or can it be applied before? I mean if we need to go
> > some global, not codec based DAPM, then there is need to prefix but not
> > if DAPM remains per codec.
> Well, the DAPM map needs to be global in some sense since it needs to
> flow between CODECs and we need board widgets which are definitely not
> fixed on an individual chip.  
> I think I'd like a firm idea of how the cross device DAPM works before
> we do anything with the prefixes since there's some overlap there (if
> only due to the fact that half the controls come from DAPM), even if the
> cross device DAPM doesn't actually work yet.  I think your current code
> is probably going to work well with DAPM but I need to have a bit of a
> think about that over the weekend.

I've made some initial progress here with DAPM by de-coupling it from
CODEC drivers. So I now have a struct dapm_context * in the codec,
platform and machine drivers. I just now need to get some time to
experiment with the best way to hook them all up.

It's currently in my L24.9 branch, although the patches are in need of
clean up and squashing so are not ready for upstream yet.

Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.

More information about the Alsa-devel mailing list