Hi Guennadi, On 02/01/2012 02:44 AM, Guennadi Liakhovetski wrote: >> V4L2_MBUS_FMT_VYUY_JPEG_1X8 > > Hmm... Are such sensors not sending this data over something like CSI-2 > with different channel IDs? In which case we just deal with two formats > cleanly. I think they could, it might be just a matter of a proper firmware. But now all that is available is only truly interleaved data, in the chunks of page or so. For a full picture I should mention that such a frame contains also embedded non image data, at the end of frame. But this can possibly be handled with a separate buffer queue, like in VBI case for instance. > Otherwise - I'm a bit sceptical about defining a new format for each pair > of existing codes. Maybe we should rather try to describe individual > formats and the way they are interleaved? In any case the end user will Yes, sounds reasonable. However the sensor specific frame is transferred as MIPI-CSI2 User Defined Data 1. So it should be possible to associate such information with the format on the media bus, for the bus receiver to be able to properly handle the data. > want them separately, right? So, at some point they will want to know what > are those two formats, that the camera has sent. I'm afraid the data will data have to be separated in user space. Moreover the user space needs to know what are resolutions for each YUV and JPEG frames. But this could be probably queried at relevant subdevs/pads. > No, I don't know yet how to describe this, proposals are welcome;-) :-) >> for interleaved VYUY and JPEG data might do, except it doesn't tell anything >> about how the data is interleaved. >> >> So maybe we could add some code describing interleaving (xxxx) >> >> V4L2_MBUS_FMT_xxxx_VYUY_JPEG_1X8 >> >> or just the sensor name instead ? > > As I said above, I would describe formats separately and the way, how they > are interleaved. BTW, this might be related to recent patches from > Laurent, introducing data layout in RAM and fixing bytesperline and > sizeimage calculations. Yes, more or less. Except of honoring 'sizeimage' the sensor needs to be queried for the required buffer frame it sends out. I'm currently doing it with a patch like this: http://www.mail-archive.com/linux-media@xxxxxxxxxxxxxxx/msg39780.html But I'm planning to change it to use a new control instead. -- 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
