From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
hverkuil@xs4all.nl, laurent.pinchart@ideasonboard.com,
bingbu.cao@intel.com
Subject: [PATCH v8 0/9] Use V4L2 mbus config for conveying link frequency
Date: Tue, 17 Dec 2024 23:54:36 +0200 [thread overview]
Message-ID: <20241217215445.901459-1-sakari.ailus@linux.intel.com> (raw)
Hi folks,
This set adds a few helpers for obtaining the link frequency from the V4L2
mbus config for devices that don't need to provide an UAPI to change it,
and finally move drivers to call v4l2_get_link_freq() on a pad.
since v7:
- Drop ctrl_to_csi() as it's now unused.
- Add patches to document how CSI-2 receiver should obtain the link
frequency, moving stopping streaming out of CSI-2 specific part and
adding a note on setting all fields in get_mbus_config() op.
- Added a patch to convert existing users of v4l2_get_link_freq() to
operate on a media pad (vs. the control handler). I'll postpone merging
this however to test it a bit as it touches a number of drivers for
which I have no hardware for.
- Revert the order or the ivsc and ipu6 patches.
- Improved documentation as discussed with Laurent in v7 review.
since v6:
- Remove comments on #else / #endif, it's trivial.
- Add a patch to convert the ipu6 driver.
since v5:
- Only support pad-based operation with CONFIG_MEDIA_CONTROLLER (1st and
2nd patches).
since v4:
- Rework documentation a little.
- Remove wrong alignment change in 2nd patch.
- Move link_freq field after the type field in struct v4l2_mbus_config.
since v3:
- Add back missing ret I accidentally removed rather than moved to the 2nd
patch.
since v2:
- Switch to V4L2 mbus config for conveying the link frequency.
since v1:
- Add a new 64-bit integer control V4L2_CID_CUR_LINK_FREQ instead of
re-using V4L2_CID_LINK_FREQ.
Sakari Ailus (9):
media: v4l: Support passing media pad argument to v4l2_get_link_freq()
media: v4l: Support obtaining link frequency via get_mbus_config
media: Documentation: Update link frequency driver documentation
media: Documentation: tx-rx: Move transmitter control out of CSI-2
part
media: Documentation: Receiver drivers should call
v4l2_get_link_freq()
media: Documentation: Add a note to set all fields in get_mbus_config
op
media: intel/ipu6: Obtain link frequency from the remote subdev pad
media: ivsc: csi: Obtain link frequency from the media pad
media: v4l: Convert the users of v4l2_get_link_freq to call it on a
pad
Documentation/driver-api/media/tx-rx.rst | 26 ++++---
drivers/media/i2c/st-mipid02.c | 5 +-
drivers/media/i2c/tc358746.c | 4 +-
drivers/media/pci/intel/ipu3/ipu3-cio2.c | 11 ++-
drivers/media/pci/intel/ipu6/ipu6-isys-csi2.c | 12 +--
drivers/media/pci/intel/ivsc/mei_csi.c | 78 +++++++------------
drivers/media/platform/cadence/cdns-csi2rx.c | 4 +-
drivers/media/platform/nxp/imx-mipi-csis.c | 5 +-
drivers/media/platform/nxp/imx8mq-mipi-csi2.c | 11 ++-
.../media/platform/qcom/camss/camss-vfe-17x.c | 8 +-
.../platform/qcom/camss/camss-vfe-gen1.c | 8 +-
drivers/media/platform/qcom/camss/camss.c | 17 ++--
drivers/media/platform/qcom/camss/camss.h | 2 +-
.../media/platform/raspberrypi/rp1-cfe/cfe.c | 4 +-
drivers/media/platform/st/stm32/stm32-csi.c | 4 +-
drivers/media/platform/ti/cal/cal-camerarx.c | 3 +-
drivers/media/platform/ti/cal/cal.c | 4 +-
drivers/media/platform/ti/cal/cal.h | 1 +
drivers/media/v4l2-core/v4l2-common.c | 32 +++++++-
include/media/v4l2-common.h | 19 ++++-
include/media/v4l2-mediabus.h | 2 +
include/media/v4l2-subdev.h | 5 +-
22 files changed, 155 insertions(+), 110 deletions(-)
base-commit: c2bb0ff95c29040483ac93b4c10fdf1bd8071b9d
--
2.39.5
next reply other threads:[~2024-12-17 21:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 21:54 Sakari Ailus [this message]
2024-12-17 21:54 ` [PATCH v8 1/9] media: v4l: Support passing media pad argument to v4l2_get_link_freq() Sakari Ailus
2024-12-20 13:09 ` Tomi Valkeinen
2025-01-08 13:14 ` Sakari Ailus
2024-12-17 21:54 ` [PATCH v8 2/9] media: v4l: Support obtaining link frequency via get_mbus_config Sakari Ailus
2024-12-20 12:59 ` Tomi Valkeinen
2025-01-08 13:53 ` Sakari Ailus
2024-12-17 21:54 ` [PATCH v8 3/9] media: Documentation: Update link frequency driver documentation Sakari Ailus
2024-12-17 21:54 ` [PATCH v8 4/9] media: Documentation: tx-rx: Move transmitter control out of CSI-2 part Sakari Ailus
2024-12-20 13:21 ` Tomi Valkeinen
2024-12-17 21:54 ` [PATCH v8 5/9] media: Documentation: Receiver drivers should call v4l2_get_link_freq() Sakari Ailus
2024-12-20 13:22 ` Tomi Valkeinen
2024-12-17 21:54 ` [PATCH v8 6/9] media: Documentation: Add a note to set all fields in get_mbus_config op Sakari Ailus
2024-12-20 13:29 ` Tomi Valkeinen
2025-01-08 13:42 ` Sakari Ailus
2024-12-17 21:54 ` [PATCH v8 7/9] media: intel/ipu6: Obtain link frequency from the remote subdev pad Sakari Ailus
2024-12-17 21:54 ` [PATCH v8 8/9] media: ivsc: csi: Obtain link frequency from the media pad Sakari Ailus
2024-12-17 21:54 ` [PATCH v8 9/9] media: v4l: Convert the users of v4l2_get_link_freq to call it on a pad Sakari Ailus
2024-12-19 11:03 ` [RESEND PATCH " Sakari Ailus
2024-12-19 12:44 ` Naushir Patuck
2025-01-02 10:49 ` Benjamin Mugnier
2024-12-20 13:19 ` [PATCH " Tomi Valkeinen
2025-01-08 12:50 ` 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=20241217215445.901459-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=hverkuil@xs4all.nl \
--cc=jacopo.mondi@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