Hi Philipp,
On Thu, Jul 4, 2019 at 6:34 AM Philipp Zabel wrote:
> Could this just be added to the end of ov5645_global_init_setting?
Just tested your suggestion and it also works.
Thanks
Hi Ezequiel,
On Wed, 2019-07-03 at 10:10 -0300, Ezequiel Garcia wrote:
> This is mostly a port of Jacopo's fix:
>
> commit aa4bb8b8838ffcc776a79f49a4d7476b82405349
> Author: Jacopo Mondi
> Date: Fri Jul 6 05:51:52 2018 -0400
>
> media: ov5640: Re-work MIPI startup sequence
>
> In the
Hi Ezequiel,
On Wed, Jul 3, 2019 at 10:10 AM Ezequiel Garcia wrote:
>
> This is mostly a port of Jacopo's fix:
>
> commit aa4bb8b8838ffcc776a79f49a4d7476b82405349
> Author: Jacopo Mondi
> Date: Fri Jul 6 05:51:52 2018 -0400
>
> media: ov5640: Re-work MIPI startup sequence
>
> In the OV
This is mostly a port of Jacopo's fix:
commit aa4bb8b8838ffcc776a79f49a4d7476b82405349
Author: Jacopo Mondi
Date: Fri Jul 6 05:51:52 2018 -0400
media: ov5640: Re-work MIPI startup sequence
In the OV5645 case, the changes are:
- Move OV5645_IO_MIPI_CTRL00 (0x300e) out of the initial s