[alsa-devel] ASoC - Support for multiple components

Liam Girdwood lrg at slimlogic.co.uk
Tue Apr 20 12:46:07 CEST 2010

On Tue, 2010-04-20 at 10:17 +0300, Peter Ujfalusi wrote:

> > 
> > I've CC'ed folks on this mail who have either contributed or maintain
> > ASoC architecture code. Please have a look at your architecture and test
> > if you can. I only have access to OMAP and pxa3xx hardware and as such
> > have only tested the changes on these two architectures only. I'd
> > appreciated anyone else testing on the other architectures too.
> Just a side note: you missed the OMAP PCM/McBSP folks from the CC: Jarkko, and 
> me ;) I'll add Jarkko to the cc...

Oops, sorry about that.

> > The changes are all purely mechanical to component registration and
> > component private data only. However, some architectures (txx9, imx,
> > s3c) required some extra effort to use the device model as they had (to
> > varying degrees) coupled their DMA and DAI code more tightly. The fsl
> > platform also required extra work around the open firmware interface.
> > Grant/Timur do we still need soc-of-simple now that all components are
> > regular devices ?
> I have one question:
> How the overlapping kcontrol names are going to handled (plain kcontrol and DAPM 
> widget names)?
> What will happen if let say you have wm8711 _and_ wm8731 in the same card?
> Both have:
> "Master Playback Volume", "Master Playback ZC Switch" in snd_kcontrol_new, and 
> also LOUT, ROUT, LHPOUT, RHPOUT, and SND_SOC_DAPM_MIXER("Output Mixer",..) in 
> snd_soc_dapm_widget.
> How the user will see these in one card?

A subsequent patch will add an ID qualifier to kcontrol names and DAPM
widget names. So we can have things like "Master Playback Volume.0" and
"Master Playback Volume.1" to differentiate the two separate controls. 


Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.

More information about the Alsa-devel mailing list