Hi, Sakari, > -----Original Message----- > From: Sakari Ailus [mailto:sakari.ailus@xxxxxxxxxxxxxxx] > Sent: Friday, August 18, 2017 2:31 PM > To: linux-media@xxxxxxxxxxxxxxx > Cc: linux-api@xxxxxxxxxxxxxxx; tfiga@xxxxxxxxxxxx; Zhi, Yong > <yong.zhi@xxxxxxxxx> > Subject: [PATCH 0/2] Add V4L2_BUF_TYPE_META_OUTPUT buffer type > > Hi folks, > > Here's a non-RFC version of the META_OUTPUT buffer type patches. > > The V4L2_BUF_TYPE_META_OUTPUT buffer type complements the metadata > buffer types support for OUTPUT buffers, capture being already supported. > This is intended for similar cases than V4L2_BUF_TYPE_META_CAPTURE but > for output buffers, e.g. device parameters that may be complex and highly > hierarchical data structure. Statistics are a current use case for metadata > capture buffers. > > Yong: could you take these to your IPU3 ImgU patchset, please? As that > would be the first user, the patches would be merged with the driver itself. > We implemented the meta format support in IPU3, the changes will be in ImgU v4, thanks!! > since RFC: > > - Fix make htmldocs build. > > - Fix CAPTURE -> OUTPUT in buffer.rst. > > - Added " for specifying how the device processes images" in the > documentation. > > Sakari Ailus (2): > v4l: Add support for V4L2_BUF_TYPE_META_OUTPUT > docs-rst: v4l: Document V4L2_BUF_TYPE_META_OUTPUT interface > > Documentation/media/uapi/v4l/buffer.rst | 3 +++ > Documentation/media/uapi/v4l/dev-meta.rst | 33 ++++++++++++++------ > ---- > Documentation/media/uapi/v4l/vidioc-querycap.rst | 3 +++ > Documentation/media/videodev2.h.rst.exceptions | 2 ++ > drivers/media/v4l2-core/v4l2-compat-ioctl32.c | 2 ++ > drivers/media/v4l2-core/v4l2-ioctl.c | 25 ++++++++++++++++++ > drivers/media/v4l2-core/videobuf2-v4l2.c | 1 + > include/media/v4l2-ioctl.h | 17 ++++++++++++ > include/uapi/linux/videodev2.h | 2 ++ > 9 files changed, 75 insertions(+), 13 deletions(-) > > -- > 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
