From: Arec Kao <arec.kao@intel.com>
To: linux-media@vger.kernel.org
Cc: sakari.ailus@linux.intel.com, andy.yeh@intel.com,
tfiga@google.com, arec.kao@intel.com
Subject: [PATCH 2/2] Re-run BLC when gain change
Date: Tue, 8 Mar 2022 11:38:39 +0800 [thread overview]
Message-ID: <20220308033839.3773-2-arec.kao@intel.com> (raw)
In-Reply-To: <20220308033839.3773-1-arec.kao@intel.com>
Changing the gain affects the black-level through the device;
the gain should therefore not be changed during a BLC procedure.
If the gain changes, then the BLC routine should be re-run
in some scenarios.
Signed-off-by: Arec Kao <arec.kao@intel.com>
---
.../userspace-api/media/v4l/ext-ctrls-image-source.rst | 5 +++++
1 file changed, 5 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..5ee53ba76d46 100644
--- a/Documentation/userspace-api/media/v4l/ext-ctrls-image-source.rst
+++ b/Documentation/userspace-api/media/v4l/ext-ctrls-image-source.rst
@@ -59,6 +59,11 @@ Image Source Control IDs
non-sensitive.
This control is required for automatic calibration of sensors/cameras.
+``V4L2_CID_BLC (integer)``
+ Changing the gain affects the black-level through the device; the gain
+ should therefore not be changed during a BLC procedure. If the gain
+ changes, the BLC routine should be re-run in some scenarios.
+
.. c:type:: v4l2_area
.. flat-table:: struct v4l2_area
--
2.17.1
next prev parent reply other threads:[~2022-03-08 2:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 3:38 [PATCH 1/2] Add a V4L2 control to allow configuring BLC from userspace Arec Kao
2022-03-08 3:38 ` Arec Kao [this message]
2022-03-08 12:13 ` [PATCH 2/2] Re-run BLC when gain change Laurent Pinchart
2022-03-08 12:48 ` Sakari Ailus
2022-05-16 9:15 ` Tomasz Figa
2022-03-08 12:12 ` [PATCH 1/2] Add a V4L2 control to allow configuring BLC from userspace Laurent Pinchart
2022-03-08 12:35 ` 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=20220308033839.3773-2-arec.kao@intel.com \
--to=arec.kao@intel.com \
--cc=andy.yeh@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@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