[alsa-devel] [PATCH 08/13] ASoC: Track which components have been registered with snd_soc_register_component()

Mark Brown broonie at kernel.org
Mon Mar 24 12:33:30 CET 2014

On Mon, Mar 24, 2014 at 11:18:05AM +0000, Charles Keepax wrote:
> On Tue, Mar 18, 2014 at 09:02:11AM +0100, Lars-Peter Clausen wrote:

> > snd_soc_unregister_component() takes the parent device of the component as a
> > parameter and then looks up the component based on this. This is a problem if
> > multiple components are registered for the same parent device. Currently drivers

> Do we have any thoughts on what might be a longer term solution
> here? Is the parent device actually the right thing to pass to
> snd_soc_unregister_component, it feels like that is probably not
> going to be enough to accurately identify the component?

It's not clear to me that in the longer term it makes sense for anything
that is a single struct device to be registering multiple components in
the first place.  In the short term we register things separately so it
makes sense to continue to support that to ease transition but it's not
clear to me that it's a good idea.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20140324/ded34301/attachment.sig>

More information about the Alsa-devel mailing list