From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Isaac Scott <isaac.scott@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rui Miguel Silva <rmfrfs@gmail.com>,
Martin Kepplinger <martink@posteo.de>,
Purism Kernel Team <kernel@puri.sm>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH v3 1/3] media: v4l: Add helper to get number of active lanes via a pad
Date: Mon, 22 Sep 2025 10:16:37 +0300 [thread overview]
Message-ID: <20250922071637.GH10540@pendragon.ideasonboard.com> (raw)
In-Reply-To: <aNDxR72CmvGofTHy@valkosipuli.retiisi.eu>
On Mon, Sep 22, 2025 at 09:48:39AM +0300, Sakari Ailus wrote:
> On Mon, Sep 15, 2025 at 02:18:33PM +0100, Isaac Scott wrote:
> > Sometimes, users will not use all of the MIPI CSI 2 lanes available when
> > connecting to the MIPI CSI receiver of their device. Add a helper
> > function that checks the mbus_config for the device driver to allow
> > users to define the number of active data lanes through the
> > get_mbus_config op.
> >
> > If the driver does not implement this op, fall back to using the number
> > of data lanes specified in device tree.
> >
> > Reviewed-by: Frank Li <Frank.Li@nxp.com>
> > Signed-off-by: Isaac Scott <isaac.scott@ideasonboard.com>
> > ---
> > drivers/media/v4l2-core/v4l2-common.c | 32 ++++++++++++++++++++++++++++++++
> > include/media/v4l2-common.h | 21 +++++++++++++++++++++
> > 2 files changed, 53 insertions(+)
> >
> > diff --git a/drivers/media/v4l2-core/v4l2-common.c b/drivers/media/v4l2-core/v4l2-common.c
> > index 6e585bc76367..2ce8407f1397 100644
> > --- a/drivers/media/v4l2-core/v4l2-common.c
> > +++ b/drivers/media/v4l2-core/v4l2-common.c
> > @@ -571,6 +571,38 @@ s64 __v4l2_get_link_freq_pad(struct media_pad *pad, unsigned int mul,
> > return __v4l2_get_link_freq_ctrl(sd->ctrl_handler, mul, div);
> > }
> > EXPORT_SYMBOL_GPL(__v4l2_get_link_freq_pad);
> > +
> > +unsigned int v4l2_get_active_data_lanes(const struct media_pad *pad,
> > + unsigned int max_data_lanes)
> > +{
> > + struct v4l2_mbus_config mbus_config = {};
> > + struct v4l2_subdev *sd;
> > + unsigned int lanes;
> > + int ret;
> > +
> > + sd = media_entity_to_v4l2_subdev(pad->entity);
> > + ret = v4l2_subdev_call(sd, pad, get_mbus_config, pad->index,
> > + &mbus_config);
> > + if (ret < 0 && ret != -ENOIOCTLCMD)
> > + return ret;
> > +
> > + /*
> > + * This relies on the mbus_config being zeroed at init time.
> > + */
This holds on a single line.
> > + if (!mbus_config.bus.mipi_csi2.num_data_lanes)
>
> I'd either use the local variable for this (lanes) either all the time, or
> not at all.
>
> > + return max_data_lanes;
> > +
> > + lanes = mbus_config.bus.mipi_csi2.num_data_lanes;
> > +
> > + if (lanes > max_data_lanes) {
> > + dev_dbg(sd->dev, "Active data lanes (%u) exceeds max (%u)\n",
> > + lanes, max_data_lanes);
> > + return -EINVAL;
> > + }
> > +
> > + return lanes;
> > +}
> > +EXPORT_SYMBOL_GPL(v4l2_get_active_data_lanes);
> > #endif /* CONFIG_MEDIA_CONTROLLER */
> >
> > /*
> > diff --git a/include/media/v4l2-common.h b/include/media/v4l2-common.h
> > index 0a43f56578bc..6af0695460ab 100644
> > --- a/include/media/v4l2-common.h
> > +++ b/include/media/v4l2-common.h
> > @@ -584,6 +584,27 @@ int v4l2_fill_pixfmt_mp(struct v4l2_pix_format_mplane *pixfmt, u32 pixelformat,
> > (pad, mul, div)
> > s64 __v4l2_get_link_freq_pad(struct media_pad *pad, unsigned int mul,
> > unsigned int div);
>
> Is your tree up to date?
We seem to be moving faster than we used to :-)
> > +
> > +/**
> > + * v4l2_get_active_data_lanes - Get number of active data lanes from driver
> > + *
> > + * @pad: The transmitter's media pad.
> > + * @max_data_lanes: The maximum number of active data lanes supported by
> > + * the MIPI CSI link in hardware. This can be configured
> > + * in device tree.
>
> I'd remove the latter sentence. Alternatively, it needs to be improved:
> there are other sources for this information than DT.
>
> > + *
> > + * This function is intended for obtaining the number of data lanes that are
> > + * actively being used by the driver for a MIPI CSI-2 device on a given media pad.
> > + * This information is derived from a mbus_config fetched from a device driver
> > + * using the get_mbus_config v4l2_subdev pad op.
> > + *
> > + * Return:
> > + * * >0: Number of active data lanes
> > + * * %-EINVAL: Number of active data lanes is invalid, as it exceeds the maximum
> > + * supported data lanes listed in device tree.
Drop "listed in the device tree" here too.
With those small issues fixed,
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > + */
> > +unsigned int v4l2_get_active_data_lanes(const struct media_pad *pad,
> > + unsigned int max_data_lanes);
> > #else
> > #define v4l2_get_link_freq(handler, mul, div) \
> > __v4l2_get_link_freq_ctrl(handler, mul, div)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2025-09-22 7:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 13:18 [PATCH v3 0/3] media: imx-mipi-csis: Get the number of active lanes from mbus_config Isaac Scott
2025-09-15 13:18 ` [PATCH v3 1/3] media: v4l: Add helper to get number of active lanes via a pad Isaac Scott
2025-09-22 6:48 ` Sakari Ailus
2025-09-22 7:16 ` Laurent Pinchart [this message]
2025-09-15 13:18 ` [PATCH v3 2/3] media: imx-mipi-csis: Store the number of data_lanes configured in dt Isaac Scott
2025-09-22 6:49 ` Sakari Ailus
2025-09-22 8:07 ` Laurent Pinchart
2025-09-15 13:18 ` [PATCH v3 3/3] media: imx-mipi-csis: Get number of active lanes via mbus_config Isaac Scott
2025-09-22 8:09 ` 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=20250922071637.GH10540@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=Frank.Li@nxp.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=isaac.scott@ideasonboard.com \
--cc=kernel@pengutronix.de \
--cc=kernel@puri.sm \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martink@posteo.de \
--cc=mchehab@kernel.org \
--cc=rmfrfs@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=sakari.ailus@iki.fi \
--cc=shawnguo@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
all inboxes | Powered by JetHome®