From: Frank Li <Frank.li@nxp.com>
To: Michael Tretter <m.tretter@pengutronix.de>
Cc: Steve Longerbeam <slongerbeam@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
linux-media@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org,
Michael Tretter <michael.tretter@pengutronix.de>
Subject: Re: [PATCH 2/2] media: staging: imx: configure src_mux in csi_start
Date: Wed, 5 Nov 2025 11:53:22 -0500 [thread overview]
Message-ID: <aQuBAmJkm1MvOUfr@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20251105-media-imx-fixes-v1-2-99e48b4f5cbc@pengutronix.de>
On Wed, Nov 05, 2025 at 04:18:50PM +0100, Michael Tretter wrote:
> After media_pipeline_start() was called, the media graph is assumed to
> be validated. It won't be validated again if a second stream starts.
>
> The imx-media-csi driver, however, changes hardware configuration in the
> link_validate() callback. This can result in started streams with
> misconfigured hardware.
>
> In the concrete example, the ipu2_csi1_mux is driven by a parallel video
> input. After the media pipeline has been started with this
> configuration, a second stream is configured to use ipu1_csi0 with
> MIPI-CSI input from imx6-mipi-csi2. This may require the reconfiguration
> of ipu1_csi0 with ipu_set_csi_src_mux(). Since the media pipeline is
> already running, link_validate won't be called, and the ipu1_csi0 won't
> be reconfigured. The resulting video is broken, because the
> ipu1_csi0_mux is misconfigured, but no error is reported.
>
> Move ipu_set_csi_src_mux from csi_link_validate to csi_start to ensure
> that input to ipu1_csi0 is configured correctly when starting the
> stream. This is a local reconfiguration in ipu1_csi0 and is possible
> while the media pipeline is running.
>
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> Fixes: 4a34ec8e470c ("[media] media: imx: Add CSI subdev driver")
> Cc: stable@vger.kernel.org
> ---
> drivers/staging/media/imx/imx-media-csi.c | 44 +++++++++++++++++--------------
> 1 file changed, 24 insertions(+), 20 deletions(-)
>
...
>
> ret = v4l2_subdev_link_validate_default(sd, link,
> @@ -1145,25 +1168,6 @@ static int csi_link_validate(struct v4l2_subdev *sd,
> return ret;
> }
>
> - mutex_lock(&priv->lock);
Is it safe to remove lock? I think put justification in commit message
about removing lock.
Frank
> -
> - is_csi2 = !is_parallel_bus(&mbus_cfg);
> - if (is_csi2) {
> - /*
> - * NOTE! It seems the virtual channels from the mipi csi-2
> - * receiver are used only for routing by the video mux's,
> - * or for hard-wired routing to the CSI's. Once the stream
> - * enters the CSI's however, they are treated internally
> - * in the IPU as virtual channel 0.
> - */
> - ipu_csi_set_mipi_datatype(priv->csi, 0,
> - &priv->format_mbus[CSI_SINK_PAD]);
> - }
> -
> - /* select either parallel or MIPI-CSI2 as input to CSI */
> - ipu_set_csi_src_mux(priv->ipu, priv->csi_id, is_csi2);
> -
> - mutex_unlock(&priv->lock);
> return ret;
> }
>
>
> --
> 2.47.3
>
prev parent reply other threads:[~2025-11-05 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 15:18 [PATCH 0/2] media: staging: imx: fix multiple video input Michael Tretter
2025-11-05 15:18 ` [PATCH 1/2] media: staging: imx: request mbus_config in csi_start Michael Tretter
2025-11-05 16:47 ` Frank Li
2025-11-05 15:18 ` [PATCH 2/2] media: staging: imx: configure src_mux " Michael Tretter
2025-11-05 15:33 ` Philipp Zabel
2025-11-05 16:53 ` Frank Li [this message]
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=aQuBAmJkm1MvOUfr@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=festevam@gmail.com \
--cc=hans.verkuil@cisco.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=mchehab@kernel.org \
--cc=michael.tretter@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--cc=slongerbeam@gmail.com \
--cc=stable@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