Hi Hans, On Tue, May 24, 2016 at 05:36:42PM +0200, Hans Verkuil wrote: > On 05/24/2016 05:28 PM, Sakari Ailus wrote: > > Hi Hans, > > > >> Should it be mentioned here that changing the video format might change > >> the buffersize? In case the buffersize is always a multiple of the width? > > > > Isn't that the case in general, as with pixel formats? buffersize could also > > be something else than a multiple of width (there's no width for metadata > > formats) due to e.g. padding required by hardware. > > Well, I don't think it is obvious that the metadata buffersize depends on the > video width. Perhaps developers who are experienced with CSI know this, but > if you know little or nothing about CSI, then it can be unexpected (hey, that > was the case for me!). > > I think it doesn't hurt to mention this relation. Ah, I think I misunderstood you first. Typically the metadata width is the same as the image data width, that's true. And it's how the hardware works. This is still visible in the media bus format and the solution belongs rather to how multiple streams over a single link are supported. It's just that setting the image media bus format affects the metadata media bus format. I guess that could be mentioned albeit it's hardware specific, on some sensors metadata width is independent of the image width. Even then this is not where I'd put it. I'd get back to the topic when documenting how the API for multiple streams over a single link works. -- Kind regards, Sakari Ailus e-mail: sakari.ailus@xxxxxx XMPP: sailus@xxxxxxxxxxxxxx -- 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
