Hi Mauro, On Wednesday 28 August 2013 06:27:52 Mauro Carvalho Chehab wrote: > Sylwester Nawrocki <s.nawrocki@xxxxxxxxxxx> escreveu: > > On 08/27/2013 06:00 PM, Mauro Carvalho Chehab wrote: > > >>> > > The thing is that you're wanting to use the clock register as a > > >>> > > way to detect that the device got initialized. > > >> > > > >> > I'm not sure to follow you there, I don't think that's how I want to > > >> > use the clock. Could you please elaborate ? > > > > > > As Sylwester pointed, the lack of clock register makes ov2640 to defer > > > probing, as it assumes that the sensor is not ready. > > > > Hmm, actually there are two drivers here - the sensor driver defers its > > probing() when a clock provided by the bridge driver is missing. Thus > > let's not misunderstand it that missing clock is used as an indication > > of the sensor not being ready. It merely means that the clock provider > > (which in this case is the bridge driver) has not initialized yet. > > It's pretty standard situation, the sensor doesn't know who provides > > the clock but it knows it needs the clock and when that's missing it > > defers its probe(). > > On an always on clock, there's no sense on defer probe. The point is that the sensor driver doesn't know whether the clock is always on or not, so it must defer the probe if the clock object isn't available (remember that even for always-on clocks the sensor driver often needs to query the clock rate). That won't happen in this case as the sensor device is instanciated by the em28xx driver, so the clock object will always be available. -- Regards, Laurent Pinchart -- 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
