From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Frieder Schrempf <frieder@fris.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rui Miguel Silva <rmfrfs@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Paul Elder <paul.elder@ideasonboard.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH v2] media: imx: imx7-media-csi: Fix error handling in imx7_csi_async_register()
Date: Wed, 15 Feb 2023 19:26:26 +0200 [thread overview]
Message-ID: <Y+0Vwm5Q0DH+RRrH@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20230215171642.2122786-1-frieder@fris.de>
Hi Frieder,
Thank you for the patch.
On Wed, Feb 15, 2023 at 06:16:38PM +0100, Frieder Schrempf wrote:
> From: Frieder Schrempf <frieder.schrempf@kontron.de>
>
> The CSI requires a connected source subdev to operate. If
> fwnode_graph_get_endpoint_by_id() fails and returns NULL, there is no
> point in going on. Print an error message and abort instead.
>
> Also we don't need to check for an existing asd. Any failure of
> v4l2_async_nf_add_fwnode_remote() should abort the probe.
>
> Suggested-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> Changes for v2:
> * Improve commit message
> * Use dev_err_probe
> ---
> drivers/media/platform/nxp/imx7-media-csi.c | 21 ++++++++++-----------
> 1 file changed, 10 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/media/platform/nxp/imx7-media-csi.c b/drivers/media/platform/nxp/imx7-media-csi.c
> index 886374d3a6ff..76ce6ff2c60a 100644
> --- a/drivers/media/platform/nxp/imx7-media-csi.c
> +++ b/drivers/media/platform/nxp/imx7-media-csi.c
> @@ -2191,19 +2191,18 @@ static int imx7_csi_async_register(struct imx7_csi *csi)
>
> ep = fwnode_graph_get_endpoint_by_id(dev_fwnode(csi->dev), 0, 0,
> FWNODE_GRAPH_ENDPOINT_NEXT);
> - if (ep) {
> - asd = v4l2_async_nf_add_fwnode_remote(&csi->notifier, ep,
> - struct v4l2_async_subdev);
> + if (!ep)
> + return dev_err_probe(csi->dev, -ENOTCONN,
> + "Failed to get remote endpoint\n");
>
> - fwnode_handle_put(ep);
> + asd = v4l2_async_nf_add_fwnode_remote(&csi->notifier, ep,
> + struct v4l2_async_subdev);
>
> - if (IS_ERR(asd)) {
> - ret = PTR_ERR(asd);
> - /* OK if asd already exists */
> - if (ret != -EEXIST)
> - return ret;
> - }
> - }
> + fwnode_handle_put(ep);
> +
> + if (IS_ERR(asd))
> + return dev_err_probe(csi->dev, PTR_ERR(asd),
> + "Failed to add remote subdev to notifier\n");
>
> csi->notifier.ops = &imx7_csi_notify_ops;
>
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2023-02-15 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 17:16 Frieder Schrempf
2023-02-15 17:26 ` Laurent Pinchart [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=Y+0Vwm5Q0DH+RRrH@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=frieder@fris.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=paul.elder@ideasonboard.com \
--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
all inboxes | Powered by JetHome®