From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
jai.luthra@ideasonboard.com
Subject: [PATCH 1/1] media: Documentation: Improve PIXEL_RATE control documentation
Date: Tue, 14 Apr 2026 13:35:59 +0300 [thread overview]
Message-ID: <20260414103559.1021712-1-sakari.ailus@linux.intel.com> (raw)
Document explicitly that the PIXEL_RATE control reflects the actual
frequency at which the pixels are read in the pixel array. It is thus
orthogonal to analogue binning.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
.../userspace-api/media/v4l/ext-ctrls-image-process.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/userspace-api/media/v4l/ext-ctrls-image-process.rst b/Documentation/userspace-api/media/v4l/ext-ctrls-image-process.rst
index 6d516f041ca2..8616bcd67270 100644
--- a/Documentation/userspace-api/media/v4l/ext-ctrls-image-process.rst
+++ b/Documentation/userspace-api/media/v4l/ext-ctrls-image-process.rst
@@ -41,6 +41,11 @@ Image Process Control IDs
The configuration of the frame rate is performed by selecting the desired
horizontal and vertical blanking. The unit of this control is Hz.
+ Note that this control isn't affected by analogue binning as the pixels are
+ still being read at the same frequency as without analogue binning, only
+ what is being read is different (a single pixel value vs. a binned pixel
+ value based on the values of two or more pixels).
+
``V4L2_CID_TEST_PATTERN (menu)``
Some capture/display/sensor devices have the capability to generate
test pattern images. These hardware specific test patterns can be
--
2.47.3
next reply other threads:[~2026-04-14 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 10:35 Sakari Ailus [this message]
2026-04-14 15:46 ` [PATCH 1/1] media: Documentation: Improve PIXEL_RATE control documentation Jacopo Mondi
2026-04-14 19:00 ` Sakari Ailus
2026-04-15 13:35 ` Jacopo Mondi
2026-04-20 21:52 ` Sakari Ailus
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=20260414103559.1021712-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=jai.luthra@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.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