From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: linux-media@vger.kernel.org,
Xavier Roumegue <xavier.roumegue@oss.nxp.com>
Subject: Re: [PATCH 0/8] Add dynamic arrays and v4l2_ctrl_modify_dimensions
Date: Fri, 8 Jul 2022 13:46:40 +0300 [thread overview]
Message-ID: <YsgLEC/RRqFA/Krs@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20220628120523.2915913-1-hverkuil-cisco@xs4all.nl>
Hi Hans,
On Tue, Jun 28, 2022 at 02:05:15PM +0200, Hans Verkuil wrote:
> This series adds support for dynamic array controls and for a
> new v4l2_ctrl_modify_dimensions() function to modify the dimensions
> of an array control by the driver.
>
> The dynamic array patches are unchanged and are already used in two
> patch series (stateless HEVC uAPI and the dw100 driver), but they are
> added here since the last 5 patches that add support for
> v4l2_ctrl_modify_dimensions() build on those.
>
> The vivid driver is also extended with such controls to make it
> possible to test this.
>
> Xavier, the v4l2_ctrl_modify_dimensions() are mostly identical to
> the patches I mailed you before and that you added to v6 of dw100.
> Just improved documentation and commit logs and a minor checkpatch
> fix. For a v7 of your driver, please use this series.
I've reviewed the whole series but 2/8 as I'm not familiar enough with
the control framework implementation for that one.
I think we also need a documentation update to indicate that drivers can
modify control dimensions, and that this will reset the control value.
It could be done in patch 6/8.
> Hans Verkuil (8):
> videodev2.h: add V4L2_CTRL_FLAG_DYNAMIC_ARRAY
> v4l2-ctrls: add support for dynamically allocated arrays.
> vivid: add dynamic array test control
> v4l2-ctrls: allocate space for arrays
> v4l2-ctrls: alloc arrays in ctrl_ref
> v4l2-ctrls: add v4l2_ctrl_modify_dimensions
> v4l2-ctrls: add change flag for when dimensions change
> vivid: add pixel_array test control
>
> .../media/v4l/vidioc-dqevent.rst | 5 +
> .../media/v4l/vidioc-queryctrl.rst | 8 +
> .../media/videodev2.h.rst.exceptions | 2 +
> drivers/media/test-drivers/vivid/vivid-core.h | 1 +
> .../media/test-drivers/vivid/vivid-ctrls.c | 29 +++
> .../media/test-drivers/vivid/vivid-vid-cap.c | 4 +
> drivers/media/v4l2-core/v4l2-ctrls-api.c | 139 ++++++++++---
> drivers/media/v4l2-core/v4l2-ctrls-core.c | 188 +++++++++++++++---
> drivers/media/v4l2-core/v4l2-ctrls-priv.h | 3 +-
> drivers/media/v4l2-core/v4l2-ctrls-request.c | 13 +-
> include/media/v4l2-ctrls.h | 90 ++++++++-
> include/uapi/linux/videodev2.h | 2 +
> 12 files changed, 413 insertions(+), 71 deletions(-)
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2022-07-08 10:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 12:05 [PATCH 0/8] Add dynamic arrays and v4l2_ctrl_modify_dimensions Hans Verkuil
2022-06-28 12:05 ` [PATCH 1/8] videodev2.h: add V4L2_CTRL_FLAG_DYNAMIC_ARRAY Hans Verkuil
2022-07-08 10:13 ` Laurent Pinchart
2022-06-28 12:05 ` [PATCH 2/8] v4l2-ctrls: add support for dynamically allocated arrays Hans Verkuil
2022-06-28 12:05 ` [PATCH 3/8] vivid: add dynamic array test control Hans Verkuil
2022-07-08 10:17 ` Laurent Pinchart
2022-06-28 12:05 ` [PATCH 4/8] v4l2-ctrls: allocate space for arrays Hans Verkuil
2022-07-08 10:21 ` Laurent Pinchart
2022-06-28 12:05 ` [PATCH 5/8] v4l2-ctrls: alloc arrays in ctrl_ref Hans Verkuil
2022-07-08 10:29 ` Laurent Pinchart
2022-06-28 12:05 ` [PATCH 6/8] v4l2-ctrls: add v4l2_ctrl_modify_dimensions Hans Verkuil
2022-07-08 10:39 ` Laurent Pinchart
2022-06-28 12:05 ` [PATCH 7/8] v4l2-ctrls: add change flag for when dimensions change Hans Verkuil
2022-07-08 10:41 ` Laurent Pinchart
2022-07-08 10:59 ` Hans Verkuil
2022-07-08 11:07 ` Laurent Pinchart
2022-07-08 11:33 ` Hans Verkuil
2022-07-08 11:38 ` Laurent Pinchart
2022-06-28 12:05 ` [PATCH 8/8] vivid: add pixel_array test control Hans Verkuil
2022-07-08 10:43 ` Laurent Pinchart
2022-07-08 10:49 ` Hans Verkuil
2022-07-08 10:46 ` Laurent Pinchart [this message]
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=YsgLEC/RRqFA/Krs@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=xavier.roumegue@oss.nxp.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