lkml.org 
[lkml]   [2019]   [Aug]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH v7 0/4] DCMI bridge support
Date
Hi Sakari, Hans,

st-mipid02 changes are already merged, thanks Sakari and sorry for
disturbance.

Still remain the V4L2_CID_LINK_FREQ for OV5640.


On 8/19/19 11:13 AM, Hugues FRUCHET wrote:
> Hi Hans, Sakari,
>
> OK to push separately the 80 char fix.
>
> There was pending related changes on st-mipid02 and ov5640 (listed
> below), do you think it's possible to take them also ?
>
>
> media: st-mipid02: add support of V4L2_CID_LINK_FREQ
> https://patchwork.linuxtv.org/patch/56969/
> State    Accepted
>
> [v2,1/3] media: st-mipid02: add support of RGB565
> https://patchwork.linuxtv.org/patch/56970/
> State    Accepted
>
> [v2,2/3] media: st-mipid02: add support of YUYV8 and UYVY8
> https://patchwork.linuxtv.org/patch/56971/
> State    Accepted
>
> [v2,3/3] media: st-mipid02: add support of JPEG
> https://patchwork.linuxtv.org/patch/56973/
> State    Accepted
>
>
> [v2] media: ov5640: add support of V4L2_CID_LINK_FREQ
> https://patchwork.linuxtv.org/patch/57215/
> State    Changes Requested
> => This change is needed to make it work the whole setup.
> => I don't know what to change here, even if this 384MHz fixed value
> seems strange, it works fine on my setup, on my opinion it's better than
> nothing. We could come back on this later on when other OV5640 CSI
> interfaces will require V4L2_CID_LINK_FREQ value.
>
> Sakari, what do you think about this ?
>
>
> BR,
> Hugues.

BR,
Hugues.
\
 
 \ /
  Last update: 2019-08-20 10:15    [W:0.080 / U:6.632 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site