On Tue, 2010-04-20 at 02:14 +0900, Mark Brown wrote: > On Mon, Apr 19, 2010 at 05:25:14PM +0100, Liam Girdwood wrote: > > > ASoC doesn't fully use the driver model for components in this changeset > > (or at all) due to the complex relationships between the individual > > components for probing() and for control of PM operations (i.e. we cant > > have pops and clicks at suspend). > > > This is not to say ASoC wont use the full driver model for components in > > the future. This work is an important step on the way to achieving this > > aim. > > The ordering requirements here mean this is a *very* open question. > Linus just nacked a bunch of stuff for 2.6.34 which would have added > some ability to waiting for components to probe stuff that things like > ASoC would need to use the driver core fully. At the minute subsystems > like ASoC which are built up of components that don't have much to do > with each other have to do something like ASoC is doing and waiting for > all the components to come online before bringing the subsystem level > devices up. Heh - I wasn't volunteering to make the changes in driver core to support this myself, but was planning to wait for someone else to do something acceptable for Linus here ;) Liam _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
