On Wed, Dec 09, 2015 at 05:09:31PM +0800, Mengdong Lin wrote: > I have no intention to replace the existing aux_devs with aux_components. > The aux_components is not for codecs and has no rtd like aux_dev. OK, but I do think that's something we *should* be doing as part of the overall move of CODECs to components and it's something that having this change implies we should be doing as an immediate thing since it's the more obvious direct use of the code (as Lars said in reply to the early draft you posted IIRC). > The purpose to introduce aux_components here is to let a soc card to load > topology info easier: > E.g. The machine driver may not define any FE DAI links explicitly but > specify an aux component. And the platform driver can implement the aux > component and let its probe ops to load the topology info. When the ASoC > core is instantiating the soc card, it must to find the aux component and > probe it (the platform component). Thus the topology info for the platform > is loaded and topology core will create widgets/controls/routes/DAIs/DAI > links. So after probing the aux components, the ASoC need to check if any > new links are created, bind them and create pcm runtimes for them. I think I'd need to see the code you're proposing here to really comment but I think it sounds like it comes back to the same thing as the above case where we're overall trying to move everything towards uniformly being components.
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
