From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, Wentong Wu <wentong.wu@intel.com>
Subject: [PATCH 0/3] Use INTEGER64 type for MEI CSI LINK_FREQ control
Date: Tue, 20 Feb 2024 15:03:36 +0200 [thread overview]
Message-ID: <20240220130339.543749-1-sakari.ailus@linux.intel.com> (raw)
Hi folks,
An integer menu isn't a useful control type for conveying the frequency
depending on an external device to the receiver. Instead, in the MEI CSI
driver, just obtain the link frequency from the upsteam sub-device and
pass it on to the receiver.
The v4l2_get_link_freq() is changed to add support for this and it's
documented as well.
Sakari Ailus (3):
media: v4l: Support obtaining link frequency from INTEGER64 controls
media: Documentation: v4l: LINK_FREQ can be an INTEGER64 control
media: ivsc: csi: Fix link frequency control behaviour
.../media/v4l/ext-ctrls-image-process.rst | 2 +-
drivers/media/pci/intel/ivsc/mei_csi.c | 30 +++++++++----------
drivers/media/v4l2-core/v4l2-common.c | 3 ++
3 files changed, 18 insertions(+), 17 deletions(-)
--
2.39.2
next reply other threads:[~2024-02-20 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 13:03 Sakari Ailus [this message]
2024-02-20 13:03 ` [PATCH 1/3] media: v4l: Support obtaining link frequency from INTEGER64 controls Sakari Ailus
2024-02-20 13:03 ` [PATCH 2/3] media: Documentation: v4l: LINK_FREQ can be an INTEGER64 control Sakari Ailus
2024-04-26 7:22 ` Hans Verkuil
2024-04-26 7:39 ` Sakari Ailus
2024-04-26 8:12 ` Hans Verkuil
2024-04-26 8:27 ` Sakari Ailus
2024-04-26 8:38 ` Hans Verkuil
2024-04-26 8:43 ` Sakari Ailus
2024-02-20 13:03 ` [PATCH 3/3] media: ivsc: csi: Fix link frequency control behaviour Sakari Ailus
2024-04-26 7:12 ` [PATCH 0/3] Use INTEGER64 type for MEI CSI LINK_FREQ control Hans Verkuil
2024-04-26 7:18 ` 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=20240220130339.543749-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=wentong.wu@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 read-only IMAP folder(s) and NNTP newsgroup(s).