Re: [PATCH v4 3/6] media: i2c: ov5640: Enable data pins on poweron for DVP mode

Hi Prabhakar, I have checked quickly both OK and KO traces an some differences are ther that we have to understand, see bottom of this mail. On 9/7/20 4:35 PM, Lad, Prabhakar wrote: > Hi Hugues, > > Thank you for the review. > > On Mon, Sep 7, 2020 at 10:44 AM Hugues FRUCHET wrote: >> >> Hi

Re: [PATCH v4 3/6] media: i2c: ov5640: Enable data pins on poweron for DVP mode

Hi Hugues, Thank you for the review. On Mon, Sep 7, 2020 at 10:44 AM Hugues FRUCHET wrote: > > Hi Prabhakar, > > Thanks for your patches, good to see one more OV5640 stakeholder > upstreaming some fixes/features. > > I'm also using a parallel setup with OV5640 connected on STM32 DCMI > camera

Re: [PATCH v4 3/6] media: i2c: ov5640: Enable data pins on poweron for DVP mode

Hi Prabhakar, Thanks for your patches, good to see one more OV5640 stakeholder upstreaming some fixes/features. I'm also using a parallel setup with OV5640 connected on STM32 DCMI camera interface. First basic tests have not shown any regressions on my side but I would like to better

[PATCH v4 3/6] media: i2c: ov5640: Enable data pins on poweron for DVP mode

During testing this sensor on iW-RainboW-G21D-Qseven platform in 8-bit DVP mode with rcar-vin bridge noticed the capture worked fine for the first run (with yavta), but for subsequent runs the bridge driver waited for the frame to be captured. Debugging further noticed the data lines were