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. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
