Moi, On Wed, Mar 23, 2022 at 10:51:04AM +0200, Tomi Valkeinen wrote: > Hi Jacopo, > > On 24/02/2022 11:42, Jacopo Mondi wrote: > > v1: > > https://patchwork.linuxtv.org/project/linux-media/list/?series=7249 > > v2: > > https://patchwork.linuxtv.org/project/linux-media/list/?series=7311 > > v3: > > https://patchwork.linuxtv.org/project/linux-media/list/?series=7385 > > v4: > > https://patchwork.linuxtv.org/project/linux-media/list/?series=7389 > > > > A branch for testing based on the most recent media-master is available at > > https://git.sr.ht/~jmondi_/linux #jmondi/media-master/ov5640-v5 > > I tested these with DRA76 EVM & CAL, using CAL's legacy non-MC mode. It > doesn't work. I think there are two problems: > > - CAL uses mbus codes like MEDIA_BUS_FMT_UYVY8_2X8 for CSI-2, not 1X16. > OV5640 used to support 2X8, but now it doesn't. > > - OV5640 sets the default code to MEDIA_BUS_FMT_UYVY8_2X8, even for CSI-2 > where it doesn't support MEDIA_BUS_FMT_UYVY8_2X8. > > I'd like to just change CAL and drop the 2X8 support and instead use 1X16, > but then any sensor that uses 2X8 would work. So I guess I need to change > the code to support both. How many drivers there are using 2X8 formats on CSI-2? I remember there has been probably few, and it should be easy to fix them. It's another question whether the 2X8 format should be kept for compatibility. Perhaps the driver could allow setting it, but should then return 1X16 when queried. -- Terveisin, Sakari Ailus
