From: Yunke Cao <yunkec@google.com>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Nicolas Dufresne <nicolas@ndufresne.ca>
Cc: Tomasz Figa <tfiga@chromium.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Ricardo Ribalda <ribalda@chromium.org>,
linux-media@vger.kernel.org, Yunke Cao <yunkec@google.com>
Subject: [PATCH v3 0/6] media: Implement UVC v1.5 ROI
Date: Wed, 18 May 2022 15:24:06 +0900 [thread overview]
Message-ID: <20220518062412.2375586-1-yunkec@google.com> (raw)
This patch set implements UVC v1.5 regioin of interest using V4L2
control API.
ROI control is consisted an auto control with type bitmask and a
rectangle control with a newly added type V4L2_CTRL_TYPE_RECT.
V4L2_CTRL_WHICH_MIN/MAX_VAL is added to support the rectangle control.
A rectangle control is also added to the vivid test driver.
Tested on two different usb cameras using v4l2-ctl and calling ioctls.
Yunke Cao (6):
media: v4l2_ctrl: Add region of interest rectangle control
media: v4l2_ctrl: Add region of interest auto control
media: v4l2_ctrl: Add V4L2_CTRL_WHICH_MIN/MAX_VAL
media: uvcvideo: implement UVC v1.5 ROI
media: uvcvideo: Initialize roi to default value
media: vivid: Add a roi rectangle control
.../userspace-api/media/drivers/uvcvideo.rst | 1 +
.../media/v4l/ext-ctrls-camera.rst | 49 ++++
.../media/v4l/vidioc-g-ext-ctrls.rst | 12 +-
.../media/videodev2.h.rst.exceptions | 3 +
drivers/media/i2c/imx214.c | 4 +-
.../media/test-drivers/vivid/vivid-ctrls.c | 34 +++
drivers/media/usb/uvc/uvc_ctrl.c | 214 ++++++++++++++++--
drivers/media/usb/uvc/uvc_v4l2.c | 12 +-
drivers/media/usb/uvc/uvcvideo.h | 10 +-
drivers/media/v4l2-core/v4l2-ctrls-api.c | 51 ++++-
drivers/media/v4l2-core/v4l2-ctrls-core.c | 155 ++++++++++++-
drivers/media/v4l2-core/v4l2-ctrls-defs.c | 7 +
drivers/media/v4l2-core/v4l2-ioctl.c | 4 +-
include/media/v4l2-ctrls.h | 32 ++-
include/uapi/linux/usb/video.h | 1 +
include/uapi/linux/uvcvideo.h | 1 +
include/uapi/linux/v4l2-controls.h | 11 +
include/uapi/linux/videodev2.h | 4 +
18 files changed, 553 insertions(+), 52 deletions(-)
--
2.36.0.550.gb090851708-goog
next reply other threads:[~2022-05-18 6:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 6:24 Yunke Cao [this message]
2022-05-18 6:24 ` [PATCH v3 1/6] media: v4l2_ctrl: Add region of interest rectangle control Yunke Cao
2022-05-19 7:49 ` Hans Verkuil
2022-05-19 8:14 ` Hans Verkuil
2022-05-19 10:39 ` Laurent Pinchart
2022-05-19 10:55 ` Hans Verkuil
2022-05-23 9:32 ` Yunke Cao
2022-05-18 6:24 ` [PATCH v3 2/6] media: v4l2_ctrl: Add region of interest auto control Yunke Cao
2022-05-19 7:52 ` Hans Verkuil
2022-05-18 6:24 ` [PATCH v3 3/6] media: v4l2_ctrl: Add V4L2_CTRL_WHICH_MIN/MAX_VAL Yunke Cao
2022-05-18 6:24 ` [PATCH v3 4/6] media: uvcvideo: implement UVC v1.5 ROI Yunke Cao
2022-05-18 6:24 ` [PATCH v3 5/6] media: uvcvideo: Initialize roi to default value Yunke Cao
2022-05-18 6:24 ` [PATCH v3 6/6] media: vivid: Add a roi rectangle control Yunke Cao
2022-05-19 8:29 ` Hans Verkuil
2022-05-19 18:29 ` [PATCH v3 0/6] media: Implement UVC v1.5 ROI Nicolas Dufresne
2022-05-19 23:55 ` Yunke Cao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220518062412.2375586-1-yunkec@google.com \
--to=yunkec@google.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=ribalda@chromium.org \
--cc=senozhatsky@chromium.org \
--cc=tfiga@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.