From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Isaac Scott <isaac.scott@ideasonboard.com>
Cc: mchehab@kernel.org, rmfrfs@gmail.com,
laurent.pinchart@ideasonboard.com, martink@posteo.de,
kernel@puri.sm, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, 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@nxp.com
Subject: Re: [PATCH v5 4/4] media: imx-mipi-csis: Support active data lanes differing from maximum
Date: Wed, 22 Oct 2025 14:13:09 +0300 [thread overview]
Message-ID: <aPi8RXHVBMB7vHQ2@kekkonen.localdomain> (raw)
In-Reply-To: <20251022102228.275627-5-isaac.scott@ideasonboard.com>
Hi Isaac,
On Wed, Oct 22, 2025 at 11:22:28AM +0100, Isaac Scott wrote:
> Call on v4l2_get_active_data_lanes() to check if the driver reports that
> the number of lanes actively used by the MIPI CSI transmitter differs to
> the maximum defined in device tree.
>
> If the number of active data lanes reported by the driver is invalid, or
> the operation is not supported, fall back to the number of allowed data
> lanes.
>
> Signed-off-by: Isaac Scott <isaac.scott@ideasonboard.com>
> ---
> drivers/media/platform/nxp/imx-mipi-csis.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/media/platform/nxp/imx-mipi-csis.c b/drivers/media/platform/nxp/imx-mipi-csis.c
> index 838a1ad123b5..637ef6e614fa 100644
> --- a/drivers/media/platform/nxp/imx-mipi-csis.c
> +++ b/drivers/media/platform/nxp/imx-mipi-csis.c
> @@ -1034,6 +1034,10 @@ static int mipi_csis_s_stream(struct v4l2_subdev *sd, int enable)
> format = v4l2_subdev_state_get_format(state, CSIS_PAD_SINK);
> csis_fmt = find_csis_format(format->code);
>
> + ret = v4l2_get_active_data_lanes(csis->source.pad,
> + csis->bus.num_data_lanes);
> + csis->num_data_lanes = ret < 0 ? csis->bus.num_data_lanes : ret;
I guess this works but should we return an error here instead?
Alternatively, the function could always return some number of lanes as
well (with a printed warning on error). I think I'd do the former though.
> +
> ret = mipi_csis_calculate_params(csis, csis_fmt);
> if (ret < 0)
> goto err_unlock;
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2025-10-22 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 10:22 [PATCH v5 0/4] media: imx-mipi-csis: Get the number of active lanes from mbus_config Isaac Scott
2025-10-22 10:22 ` [PATCH v5 1/4] media: v4l: Add helper to get number of active lanes via a pad Isaac Scott
2025-10-22 10:22 ` [PATCH v5 2/4] media: imx-mipi-csis: Move redundant debug print in probe Isaac Scott
2025-10-26 21:05 ` Laurent Pinchart
2025-10-22 10:22 ` [PATCH v5 3/4] media: imx-mipi-csis: Add num_data_lanes to mipi_csis_device Isaac Scott
2025-10-22 14:59 ` Frank Li
2025-10-26 21:07 ` Laurent Pinchart
2025-10-22 10:22 ` [PATCH v5 4/4] media: imx-mipi-csis: Support active data lanes differing from maximum Isaac Scott
2025-10-22 11:13 ` Sakari Ailus [this message]
2025-10-26 21:11 ` Laurent Pinchart
2025-10-22 15:00 ` Frank Li
2025-10-22 16:21 ` Bryan O'Donoghue
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=aPi8RXHVBMB7vHQ2@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.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=laurent.pinchart@ideasonboard.com \
--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=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