From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [ANN] Meeting minutes of the Cambourne meeting Date: Tue, 30 Aug 2011 15:00:51 +0100 Message-ID: <20110830140051.GH2061@opensource.wolfsonmicro.com> References: <201107261647.19235.laurent.pinchart@ideasonboard.com> <201108081750.07000.laurent.pinchart@ideasonboard.com> <4E5A2657.7030605@gmail.com> <201108291508.59649.laurent.pinchart@ideasonboard.com> <20110830134148.GA14976@sirena.org.uk> <20110830135609.GC1355@ponder.secretlab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20110830135609.GC1355@ponder.secretlab.ca> Sender: linux-media-owner@vger.kernel.org To: Grant Likely Cc: Guennadi Liakhovetski , Tomasz Stanislawski , Sylwester Nawrocki , Sakari Ailus , Mauro Carvalho Chehab , devicetree-discuss@lists.ozlabs.org, linux-media , Hans Verkuil , Laurent Pinchart , Sylwester Nawrocki , Marek Szyprowski , Tuukka Toivonen List-Id: devicetree@vger.kernel.org On Tue, Aug 30, 2011 at 07:56:09AM -0600, Grant Likely wrote: > On Tue, Aug 30, 2011 at 02:41:48PM +0100, Mark Brown wrote: > > The events should only be generated after the probe() has succeeded so > > if the driver talks to the hardware then it can fail probe() if need be. > I'm a bit confused here. Which events are you referring to, and which > .probe call? (the i2c/spi/whatever probe, or the aggregate v4l2 probe?) There's some driver model core level notifiers that are generated when things manage to bind (postdating all the ASoC stuff for this IIRC, and not covering the suspend/resume ordering issues). Actually, thinking about it they may be per bus.