From mboxrd@z Thu Jan 1 00:00:00 1970 From: Liam Girdwood Subject: Re: ASoC - Support for multiple components Date: Mon, 19 Apr 2010 18:23:03 +0100 Message-ID: <1271697783.3208.438.camel@odin> References: <1271686144.3208.305.camel@odin> <1271694314.3208.426.camel@odin> <20100419171418.GD29819@opensource.wolfsonmicro.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-ww0-f51.google.com (mail-ww0-f51.google.com [74.125.82.51]) by alsa0.perex.cz (Postfix) with ESMTP id 3F55B247F5 for ; Mon, 19 Apr 2010 19:23:31 +0200 (CEST) Received: by wwb22 with SMTP id 22so243400wwb.38 for ; Mon, 19 Apr 2010 10:23:30 -0700 (PDT) In-Reply-To: <20100419171418.GD29819@opensource.wolfsonmicro.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Mark Brown Cc: vbarinov , alsa-devel , Joonyoung Shim , Timur Tabi , mano@roarinelk.homelinux.net, "Candelaria Villareal, Jorge" , Haojian Zhuang , dg@emlix.com, Grant Likely , Sedji Gaouaou , Cliff Cai , ben-linux , Kuninori Morimoto , "kyungmin.park" , Sascha Hauer , anemo@mba.ocn.ne.jp List-Id: alsa-devel@alsa-project.org 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