From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Ming Qian <ming.qian@nxp.com>, mchehab@kernel.org
Cc: yunkec@google.com, nicolas@ndufresne.ca, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
xiahong.bao@nxp.com, ming.zhou@nxp.com, eagle.zhou@nxp.com,
tao.jiang_2@nxp.com, ming.qian@oss.nxp.com, imx@lists.linux.dev,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC v3 2/4] media: vivid: Add an rectangle control
Date: Mon, 28 Oct 2024 08:33:57 +0100 [thread overview]
Message-ID: <269ea671-e7cb-41fa-95a8-6d0a4cffff46@xs4all.nl> (raw)
In-Reply-To: <20241022084040.3390878-3-ming.qian@nxp.com>
On 22/10/2024 10:40, Ming Qian wrote:
> From: Yunke Cao <yunkec@google.com>
>
> This control represents a generic read/write rectangle.
> It supports V4L2_CTRL_WHICH_MIN/MAX_VAL.
>
> Signed-off-by: Yunke Cao <yunkec@google.com>
> Reviewed-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
This patch should come after patch 3/4 since it relies on the new
V4L2_CTRL_FLAG_HAS_WHICH_MIN_MAX flag introduced in 3/4.
Regards,
Hans
> ---
> .../media/test-drivers/vivid/vivid-ctrls.c | 34 +++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
> diff --git a/drivers/media/test-drivers/vivid/vivid-ctrls.c b/drivers/media/test-drivers/vivid/vivid-ctrls.c
> index 8bb38bc7b8cc..bed5f4fb0c69 100644
> --- a/drivers/media/test-drivers/vivid/vivid-ctrls.c
> +++ b/drivers/media/test-drivers/vivid/vivid-ctrls.c
> @@ -37,6 +37,7 @@
> #define VIVID_CID_U8_PIXEL_ARRAY (VIVID_CID_CUSTOM_BASE + 14)
> #define VIVID_CID_S32_ARRAY (VIVID_CID_CUSTOM_BASE + 15)
> #define VIVID_CID_S64_ARRAY (VIVID_CID_CUSTOM_BASE + 16)
> +#define VIVID_CID_RECT (VIVID_CID_CUSTOM_BASE + 17)
>
> #define VIVID_CID_VIVID_BASE (0x00f00000 | 0xf000)
> #define VIVID_CID_VIVID_CLASS (0x00f00000 | 1)
> @@ -360,6 +361,38 @@ static const struct v4l2_ctrl_config vivid_ctrl_ro_int32 = {
> .step = 1,
> };
>
> +static const struct v4l2_rect rect_def = {
> + .top = 100,
> + .left = 200,
> + .width = 300,
> + .height = 400,
> +};
> +
> +static const struct v4l2_rect rect_min = {
> + .top = 0,
> + .left = 0,
> + .width = 1,
> + .height = 1,
> +};
> +
> +static const struct v4l2_rect rect_max = {
> + .top = 0,
> + .left = 0,
> + .width = 1000,
> + .height = 2000,
> +};
> +
> +static const struct v4l2_ctrl_config vivid_ctrl_rect = {
> + .ops = &vivid_user_gen_ctrl_ops,
> + .id = VIVID_CID_RECT,
> + .name = "Rect",
> + .type = V4L2_CTRL_TYPE_RECT,
> + .flags = V4L2_CTRL_FLAG_HAS_WHICH_MIN_MAX,
> + .p_def.p_const = &rect_def,
> + .p_min.p_const = &rect_min,
> + .p_max.p_const = &rect_max,
> +};
> +
> /* Framebuffer Controls */
>
> static int vivid_fb_s_ctrl(struct v4l2_ctrl *ctrl)
> @@ -1685,6 +1718,7 @@ int vivid_create_controls(struct vivid_dev *dev, bool show_ccs_cap,
> dev->int_menu = v4l2_ctrl_new_custom(hdl_user_gen, &vivid_ctrl_int_menu, NULL);
> dev->ro_int32 = v4l2_ctrl_new_custom(hdl_user_gen, &vivid_ctrl_ro_int32, NULL);
> v4l2_ctrl_new_custom(hdl_user_gen, &vivid_ctrl_area, NULL);
> + v4l2_ctrl_new_custom(hdl_user_gen, &vivid_ctrl_rect, NULL);
> v4l2_ctrl_new_custom(hdl_user_gen, &vivid_ctrl_u32_array, NULL);
> v4l2_ctrl_new_custom(hdl_user_gen, &vivid_ctrl_u32_dyn_array, NULL);
> v4l2_ctrl_new_custom(hdl_user_gen, &vivid_ctrl_u16_matrix, NULL);
next prev parent reply other threads:[~2024-10-28 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 8:40 [RFC v3 0/4] Add video encoder ROI ctrls Ming Qian
2024-10-22 8:40 ` [RFC v3 1/4] media: v4l2_ctrl: Add V4L2_CTRL_TYPE_RECT Ming Qian
2024-10-22 8:40 ` [RFC v3 2/4] media: vivid: Add an rectangle control Ming Qian
2024-10-28 7:33 ` Hans Verkuil [this message]
2024-10-22 8:40 ` [RFC v3 3/4] media: v4l2-ctrls: add support for V4L2_CTRL_WHICH_MIN/MAX_VAL Ming Qian
2024-10-22 8:40 ` [RFC v3 4/4] media: v4l2-ctrls: Add video encoder ROI ctrls Ming Qian
2024-10-28 7:55 ` Hans Verkuil
2024-10-28 7:57 ` [RFC v3 0/4] " Hans Verkuil
2024-10-29 2:21 ` Ming Qian(OSS)
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=269ea671-e7cb-41fa-95a8-6d0a4cffff46@xs4all.nl \
--to=hverkuil-cisco@xs4all.nl \
--cc=eagle.zhou@nxp.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ming.qian@nxp.com \
--cc=ming.qian@oss.nxp.com \
--cc=ming.zhou@nxp.com \
--cc=nicolas@ndufresne.ca \
--cc=s.hauer@pengutronix.de \
--cc=tao.jiang_2@nxp.com \
--cc=xiahong.bao@nxp.com \
--cc=yunkec@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®