Re: question about v4l2_subdev

2010-06-07 Thread Sedji Gaouaou
Hi, Look at drivers/media/video/cafe_ccic.c And examine cafe_pci_probe() and the definition and use of the sensor_call() macro. Also note $ grep -Ril ov7670 drivers/media/video/* will show you in what drivers, the ov7670 might be used. I had a look at cafe_ccic.c and also at vpi

Re: question about v4l2_subdev

2010-06-04 Thread Andy Walls
On Tue, 2010-06-01 at 10:14 +0200, Sedji Gaouaou wrote: > Hi, > > > > > > 1. Something first should call v4l2_device_register() on a v4l2_device > > object. (Typically there is only one v4l2_device object per "bridge" > > chip between the PCI, PCIe, or USB bus and the subdevices, even if that >

Re: question about v4l2_subdev

2010-06-01 Thread David Ellingsworth
On Tue, Jun 1, 2010 at 10:04 AM, Sedji Gaouaou wrote: > Hi, > > Sorry to bother you again, but here is the situation: > I have 2 drivers: an ov2640 driver and my atmel driver. > Basically the ov2640 driver is the same as the ov7670 driver. > > So what I don't know is how to call the ov2640 functio

Re: question about v4l2_subdev

2010-06-01 Thread Sedji Gaouaou
Hi, Sorry to bother you again, but here is the situation: I have 2 drivers: an ov2640 driver and my atmel driver. Basically the ov2640 driver is the same as the ov7670 driver. So what I don't know is how to call the ov2640 functions(such as set format) in my atmel driver. In the ov2640 I used

Re: question about v4l2_subdev

2010-06-01 Thread Sedji Gaouaou
Hi, 1. Something first should call v4l2_device_register() on a v4l2_device object. (Typically there is only one v4l2_device object per "bridge" chip between the PCI, PCIe, or USB bus and the subdevices, even if that bridge chip has more than one I2C master implementation.) 2. Then, for subde

Re: question about v4l2_subdev

2010-05-31 Thread Andy Walls
On Mon, 2010-05-31 at 17:38 +0200, Sedji Gaouaou wrote: > Hi, > > I am currently working on the atmel video driver, and I am facing a issue. > I have written a driver for the ov2640 omnivison sensor(enclosed). In > the ov2640 driver I am using the v4l2_subdev API. The point is I don't > how how