Hi Hugues,
On Thu, May 17, 2018 at 01:29:24PM +, Hugues FRUCHET wrote:
> No special modification of v4l2-ctl, I'm using currently v4l-utils 1.12.3.
> What output do you have ?
The same one, without the resolution and framerate. I'm pretty sure
this is a driver issue and not an usperspace
Hi Maxime,
Thanks for fixes !
No special modification of v4l2-ctl, I'm using currently v4l-utils 1.12.3.
What output do you have ?
Best regards,
Hugues.
On 05/17/2018 10:52 AM, Maxime Ripard wrote:
> Hi Hugues,
>
> On Tue, May 15, 2018 at 01:33:55PM +, Hugues FRUCHET wrote:
>> I've taken
Hi Hugues,
On Tue, May 15, 2018 at 01:33:55PM +, Hugues FRUCHET wrote:
> I've taken the whole serie and made some tests on STM32 platform using
> DVP parallel interface.
> Now JPEG is OK and I've not seen any regressions appart on framerate
> control linked to this current patchset.
Thanks
Hi Maxime,
I've taken the whole serie and made some tests on STM32 platform using
DVP parallel interface.
Now JPEG is OK and I've not seen any regressions appart on framerate
control linked to this current patchset.
Here are issues observed around framerate control:
1) Framerate enumeration is
Now that we have everything in place to compute the clock rate at runtime,
we can enable the 60fps framerate for the mode we tested it with.
Signed-off-by: Maxime Ripard
---
drivers/media/i2c/ov5640.c | 33 +
1 file changed, 25