From: Benjamin Bara <bbara93@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>
Cc: laurent.pinchart@ideasonboard.com, jacopo.mondi@ideasonboard.com,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Benjamin Bara <benjamin.bara@skidata.com>
Subject: [PATCH 0/2] media: uapi: Add V4L2_CID_VTOTAL control
Date: Fri, 09 Jun 2023 15:15:54 +0200 [thread overview]
Message-ID: <20230609-v4l2-vtotal-v1-0-4b7dee7e073e@skidata.com> (raw)
Hi!
This series adds a new control for the vertical total time.
As camera sensors usually have registers regarding the total time and
not the blanking time, this would simplify driver implementations and
could therefore be seen as a replacement or upgrade for V4L2_CID_VBLANK.
Additionally, its value is independent from format changes and therefore
simplifies calculations in user space.
2/2 implements it for the imx290, basically extending the current
V4L2_CID_VBLANK implementation.
---
Benjamin Bara (2):
media: uapi: Add V4L2_CID_VTOTAL control
media: i2c: imx290: Add support for V4L2_CID_VTOTAL
.../media/v4l/ext-ctrls-image-source.rst | 6 +++
drivers/media/i2c/imx290.c | 47 ++++++++++++++++------
drivers/media/v4l2-core/v4l2-ctrls-defs.c | 1 +
include/uapi/linux/v4l2-controls.h | 1 +
4 files changed, 43 insertions(+), 12 deletions(-)
---
base-commit: 9561de3a55bed6bdd44a12820ba81ec416e705a7
change-id: 20230609-v4l2-vtotal-eb15d37cafea
Best regards,
--
Benjamin Bara <benjamin.bara@skidata.com>
next reply other threads:[~2023-06-09 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 13:15 Benjamin Bara [this message]
2023-06-09 13:15 ` [PATCH 1/2] media: uapi: Add V4L2_CID_VTOTAL control Benjamin Bara
2023-06-09 14:03 ` Dave Stevenson
2023-06-09 13:15 ` [PATCH 2/2] media: i2c: imx290: Add support for V4L2_CID_VTOTAL Benjamin Bara
2023-06-09 14:21 ` Dave Stevenson
2023-06-09 14:56 ` Benjamin Bara
2023-06-09 15:41 ` Dave Stevenson
2023-06-23 23:28 ` Laurent Pinchart
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=20230609-v4l2-vtotal-v1-0-4b7dee7e073e@skidata.com \
--to=bbara93@gmail.com \
--cc=benjamin.bara@skidata.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mchehab@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 read-only IMAP folder(s) and NNTP newsgroup(s).