So it's a matter about getting the datasheet for the image sensor and then adding a new mode (array of reg_value structs) to the driver?
Best, Jacob -----Oprindelig meddelelse----- Fra: Eric Nelson [mailto:[email protected]] Sendt: 16. september 2014 16:00 Til: Daiane Angolini; Jacob Pedersen Cc: [email protected] Emne: Re: [meta-freescale] OV5640 MIPI-CSI2 driver - why the limitations? On 09/16/2014 06:43 AM, Daiane Angolini wrote: > On Tue, Sep 16, 2014 at 10:25 AM, Jacob Pedersen <[email protected]> > wrote: >> Hi folks, >> >> >> >> I'm using a OmniVision OV5640 MIPI-CSI2 image sensor with a iMX6 Quad >> board, and I'm doing some computer vision applications. I'm curious >> to know why the driver for the OV5640 sensor is limited to 30 fps, >> even though the sensor can do 60 fps at 720p and 90 fps at VGA? As >> far as I can see in the driver, the frame rate is clamped to maximum 30 fps. >> >> >> >> Is there a technical reason, or is it just because it hasn't been >> updated for all the supported modes? >> >> >> >> The driver also limits the available image formats, which makes one >> required to do the conversion in software or (as in my case) using >> the IPU. The IPU is fairly fast to do the simple UYVY to RGB24 >> conversion, but still slower than just getting an RGB image from the sensor. > > This limitation is due to the camera device driver. Only few > configurations are implemented. > Those I2C blobs are pretty difficult to get right! Regards, Eric -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
