On Tue, 19 Mar 2019 17:37:59 +0000 Brian Starkey <Brian.Starkey@xxxxxxx> wrote: > Hi Boris, > > On Tue, Mar 19, 2019 at 03:52:42PM +0100, Boris Brezillon wrote: > > This is part of the multiplanar and singleplanar unification process. > > v4l2_ext_pix_format is supposed to work for both cases. > > > > We also add the concept of modifiers already employed in DRM to expose > > HW-specific formats (like tiled or compressed formats) and allow > > exchanging this information with the DRM subsystem in a consistent way. > > I'm quite happy to see modifiers working their way into v4l2, thank > you for picking up that torch. > > I didn't see anything about format enumeration here - do you have any > thoughts on how you think it would work? You mean extending format enumeration to also expose supported modifiers? I intentionally left that on the side as my primary goal was not to support modifiers. One solution would be to mimic the DRM approach [1] where each modifier is attached a bitmap encoding which formats they can be applied to. But, if the number of formats and modifiers is relatively small, we can go for something simpler to parse with an EXT_ENUMFMT that would return the list of supported formats and for each format entry the number of modifiers that can be applied to this format. With another ioctl (V4L2_FMT_ENUM_MODS?) you would retrieve the modifiers that can be applied to a specific format. [1]https://elixir.bootlin.com/linux/v5.1-rc1/source/include/uapi/drm/drm_mode.h#L779
