Hi Vincent, On 10/09/2012 03:36 PM, Vincent ABRIOU wrote: > Hi Sylwester, > > I'm wondering why don't you simply define V4L2_MBUS_FMT_UYVY_JPEG_1X8 > without any reference to your camera? Because it's not a plain UYVY/JPEG data. There is an additional meta-data that follows interleaved UYVY/JPEG. It's all on a single User Defined MIPI CSI-2 DT. In addition to that there is some more meta data transmitted on MIPI CSI-2 Embedded Data DT. If there was no meta-data present at the User Defined DT, then we could think about using generic V4L2_MBUS_FMT_UYVY_JPEG_1X8 pixel code and handling the meta-data on separate DT with the frame_desc calls. Anyway this S5C media bus format is an experimental thing and if there are cameras generating plain JPEG/YUV we need to search for better, more generic solution. > Indeed, many other cameras could support Jpeg interleaved with YUV and it will > avoid to define a new media bus type for every cameras integrated under V4L2 > supporting JPEG/YUV interleaving feature. Yes, we also need some interface to configure both streams, e.g. image resolutions independently. Still having separate pixel codes for pairs of JPEG and something else seems not optimal. Nevertheless I can't think of any better solution right now, so applications are able to configure selected format at a camera subdev. I'm also wondering what are the interleaving methods in case of various cameras. Even though they interleave same 2 standard formats, the way how the interleaving happens could differ, couldn't it ? Such information probably cannot be easily contained in the meta-data, unless there is some standard (header) format for it. > Thank you for your feedback. > > Regards, > -- > Vincent Abriou -- Regards, Sylwester -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
