From: Ricardo Ribalda Delgado <ricardo@ribalda.com>
To: Philipp Zabel <p.zabel@pengutronix.de>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Jacopo Mondi <jacopo@jmondi.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Ricardo Ribalda Delgado <ribalda@kernel.org>
Subject: [PATCH v6 6/7] Documentation: media: Describe V4L2_CID_UNIT_CELL_SIZE
Date: Fri, 20 Sep 2019 15:51:36 +0200 [thread overview]
Message-ID: <20190920135137.10052-7-ricardo@ribalda.com> (raw)
In-Reply-To: <20190920135137.10052-1-ricardo@ribalda.com>
From: Ricardo Ribalda Delgado <ribalda@kernel.org>
New control to pass to userspace the width/height of a pixel. Which is
needed for calibration and lens selection.
Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
Signed-off-by: Ricardo Ribalda Delgado <ribalda@kernel.org>
---
Documentation/media/uapi/v4l/ext-ctrls-image-source.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/media/uapi/v4l/ext-ctrls-image-source.rst b/Documentation/media/uapi/v4l/ext-ctrls-image-source.rst
index 2c3ab5796d76..033672dcb43d 100644
--- a/Documentation/media/uapi/v4l/ext-ctrls-image-source.rst
+++ b/Documentation/media/uapi/v4l/ext-ctrls-image-source.rst
@@ -55,3 +55,12 @@ Image Source Control IDs
``V4L2_CID_TEST_PATTERN_GREENB (integer)``
Test pattern green (next to blue) colour component.
+
+``V4L2_CID_UNIT_CELL_SIZE (struct)``
+ This control returns the unit cell size in nanometres. The struct
+ :c:type:`v4l2_area` provides the width and the height in separated
+ fields to take into consideration asymmetric pixels and/or hardware
+ binning.
+ The unit cell consists of the whole area of the pixel, sensitive and
+ non-sensitive.
+ This control is required for automatic calibration sensors/cameras.
--
2.23.0
next prev parent reply other threads:[~2019-09-20 13:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 13:51 [PATCH v6 0/7] Implement UNIT_CELL_SIZE control Ricardo Ribalda Delgado
2019-09-20 13:51 ` [PATCH v6 1/7] media: v4l2-core: Implement v4l2_ctrl_new_std_compound Ricardo Ribalda Delgado
2019-09-25 8:19 ` Jacopo Mondi
2019-09-25 20:55 ` Ricardo Ribalda Delgado
2019-09-20 13:51 ` [PATCH v6 2/7] Documentation: v4l2_ctrl_new_std_compound Ricardo Ribalda Delgado
2019-09-25 8:22 ` Jacopo Mondi
2019-09-25 21:00 ` Ricardo Ribalda Delgado
2019-09-20 13:51 ` [PATCH v6 3/7] media: add V4L2_CTRL_TYPE_AREA control type Ricardo Ribalda Delgado
2019-09-25 8:30 ` Jacopo Mondi
2019-09-20 13:51 ` [PATCH v6 4/7] Documentation: media: Document V4L2_CTRL_TYPE_AREA Ricardo Ribalda Delgado
2019-09-25 8:34 ` Jacopo Mondi
2019-09-25 21:08 ` Ricardo Ribalda Delgado
2019-09-20 13:51 ` [PATCH v6 5/7] media: add V4L2_CID_UNIT_CELL_SIZE control Ricardo Ribalda Delgado
2019-09-20 13:51 ` Ricardo Ribalda Delgado [this message]
2019-09-20 13:51 ` [PATCH v6 7/7] media: imx214: Add new control with V4L2_CID_UNIT_CELL_SIZE Ricardo Ribalda Delgado
2019-09-25 9:25 ` Jacopo Mondi
2019-09-25 21:15 ` Ricardo Ribalda Delgado
2019-09-27 7:14 ` Hans Verkuil
2019-09-27 7:33 ` Ricardo Ribalda Delgado
2019-09-27 7:52 ` Hans Verkuil
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=20190920135137.10052-7-ricardo@ribalda.com \
--to=ricardo@ribalda.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jacopo@jmondi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=ribalda@kernel.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 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).