Am 17.08.2013 12:51, schrieb Guennadi Liakhovetski: > Hi Frank, > As I mentioned on the list, I'm currently on a holiday, so, replying briefly. Sorry, I missed that (can't read all mails on the list). > Since em28xx is a USB device, I conclude, that it's supplying clock to its components including the ov2640 sensor. So, yes, I think the driver should export a V4L2 clock. Ok, so it's mandatory on purpose ? I'll take a deeper into the v4l2-clk code and the em28xx/ov2640/soc-camera interaction this week. Have a nice holiday ! Regards, Frank > Thanks > Guennadi > > > -----Original Message----- > From: "Frank Schäfer" <fschaefer.oss@xxxxxxxxxxxxxx> > To: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>, Linux Media Mailing List <linux-media@xxxxxxxxxxxxxxx> > Sent: Fr., 16 Aug 2013 21:03 > Subject: em28xx + ov2640 and v4l2-clk > > Hi Guennadi, > > since commit 9aea470b399d797e88be08985c489855759c6c60 "soc-camera: > switch I2C subdevice drivers to use v4l2-clk", the em28xx driver fails > to register the ov2640 subdevice (if needed). > The reason is that v4l2_clk_get() fails in ov2640_probe(). > Does the em28xx driver have to register a (pseudo ?) clock first ? > > Regards, > Frank -- 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
