From: Mirela Rabulea <mirela.rabulea@nxp.com>
To: mchehab@kernel.org, sakari.ailus@linux.intel.com,
hverkuil-cisco@xs4all.nl,
laurent.pinchart+renesas@ideasonboard.com, ribalda@chromium.org,
jai.luthra@ideasonboard.com, laurentiu.palcu@nxp.com
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
LnxRevLi@nxp.com, julien.vuillaumier@nxp.com,
celine.laurencin@nxp.com
Subject: [RFC 2/2] Documentation: media: Describe exposure and gain controls for multiple captures
Date: Fri, 11 Jul 2025 01:05:44 +0300 [thread overview]
Message-ID: <20250710220544.89066-3-mirela.rabulea@nxp.com> (raw)
In-Reply-To: <20250710220544.89066-1-mirela.rabulea@nxp.com>
The standard controls for exposure and gains allow a
single value, for a single capture. For sensors with HDR
capabilities or context switching, this is not enough, so
add new controls that allow multiple values, one for each
capture.
Signed-off-by: Mirela Rabulea <mirela.rabulea@nxp.com>
---
.../media/v4l/ext-ctrls-image-source.rst | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/Documentation/userspace-api/media/v4l/ext-ctrls-image-source.rst b/Documentation/userspace-api/media/v4l/ext-ctrls-image-source.rst
index 71f23f131f97..6efdb58dacf5 100644
--- a/Documentation/userspace-api/media/v4l/ext-ctrls-image-source.rst
+++ b/Documentation/userspace-api/media/v4l/ext-ctrls-image-source.rst
@@ -92,3 +92,15 @@ Image Source Control IDs
representing a gain of exactly 1.0. For example, if this default value
is reported as being (say) 128, then a value of 192 would represent
a gain of exactly 1.5.
+
+``V4L2_CID_EXPOSURE_MULTI (__u32 array)``
+ Same as V4L2_CID_EXPOSURE, but for multiple exposure sensors. Each
+ element of the array holds the exposure value for one capture.
+
+``V4L2_CID_AGAIN_MULTI (__u32 array)``
+ Same as V4L2_CID_ANALOGUE_GAIN, but for multiple exposure sensors. Each
+ element of the array holds the analog gain value for one capture.
+
+``V4L2_CID_DGAIN_MULTI (__u32 array)``
+ Same as V4L2_CID_DIGITAL_GAIN, but for multiple exposure sensors. Each
+ element of the array holds the digital gain value for one capture.
--
2.43.0
next prev parent reply other threads:[~2025-07-10 22:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 22:05 [RFC 0/2] Add standard exposure and gain controls for multiple captures Mirela Rabulea
2025-07-10 22:05 ` [RFC 1/2] media: Add " Mirela Rabulea
2025-07-10 22:05 ` Mirela Rabulea [this message]
2025-07-16 0:07 ` [RFC 2/2] Documentation: media: Describe " Laurent Pinchart
2025-07-20 19:02 ` Mirela Rabulea
2025-07-23 13:49 ` Laurent Pinchart
2025-07-24 9:33 ` Mirela Rabulea
2025-07-27 20:27 ` Laurent Pinchart
2025-07-28 13:34 ` Mirela Rabulea
2025-07-25 9:05 ` hans
2025-07-15 23:59 ` [RFC 0/2] Add standard " Laurent Pinchart
2025-07-16 0:12 ` Laurent Pinchart
2025-07-20 18:56 ` Mirela Rabulea
2025-07-22 9:53 ` Julien Vuillaumier
2025-07-23 15:02 ` Laurent Pinchart
2025-07-25 9:01 ` hans
2025-07-25 9:27 ` Laurent Pinchart
2025-07-22 8:46 ` Julien Vuillaumier
2025-07-23 14:00 ` Laurent Pinchart
2025-07-28 15:42 ` Mirela Rabulea
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=20250710220544.89066-3-mirela.rabulea@nxp.com \
--to=mirela.rabulea@nxp.com \
--cc=LnxRevLi@nxp.com \
--cc=celine.laurencin@nxp.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jai.luthra@ideasonboard.com \
--cc=julien.vuillaumier@nxp.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurentiu.palcu@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).