Let userspace specify a request ID when getting or setting formats. The
support is limited to the multi-planar API at the moment, extending it
to the single-planar API is possible if needed.

>From a userspace point of view the API change is also minimized and
doesn't require any new ioctl.

Signed-off-by: Laurent Pinchart <laurent.pinchart+rene...@ideasonboard.com>
---
 include/uapi/linux/videodev2.h | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
index 47c1b2733ecd..b776ff027f5a 100644
--- a/include/uapi/linux/videodev2.h
+++ b/include/uapi/linux/videodev2.h
@@ -1977,6 +1977,7 @@ struct v4l2_plane_pix_format {
  * @ycbcr_enc:         enum v4l2_ycbcr_encoding, Y'CbCr encoding
  * @quantization:      enum v4l2_quantization, colorspace quantization
  * @xfer_func:         enum v4l2_xfer_func, colorspace transfer function
+ * @request:           request ID
  */
 struct v4l2_pix_format_mplane {
        __u32                           width;
@@ -1991,7 +1992,8 @@ struct v4l2_pix_format_mplane {
        __u8                            ycbcr_enc;
        __u8                            quantization;
        __u8                            xfer_func;
-       __u8                            reserved[7];
+       __u8                            reserved[3];
+       __u32                           request;
 } __attribute__ ((packed));
 
 /**
-- 
2.4.10

Reply via email to