From: Dan Carpenter <dan.carpenter@linaro.org>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Mathis Foerst <mathis.foerst@mt.com>,
linux-kernel@vger.kernel.org,
Steve Longerbeam <slongerbeam@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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-staging@lists.linux.dev,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
manuel.traut@mt.com, mathis.foerst@zuehlke.com
Subject: Re: [PATCH v1 1/1] media: imx: csi: Parse link configuration from fw_node
Date: Thu, 6 Mar 2025 22:07:20 +0300 [thread overview]
Message-ID: <84aa2d87-d7f1-46c9-b28d-6f0e9a78788d@stanley.mountain> (raw)
In-Reply-To: <Z8nOTrjEW_OYBGlq@valkosipuli.retiisi.eu>
On Thu, Mar 06, 2025 at 04:33:18PM +0000, Sakari Ailus wrote:
> Hi Mathis,
>
> Thanks for the patch.
>
> On Wed, Mar 05, 2025 at 12:38:02PM +0100, Mathis Foerst wrote:
> > The imx-media-csi driver requires upstream camera drivers to implement
> > the subdev-pad-op "get_mbus_config" [0]. Camera drivers that don't
> > implement this function are not usable on the i.MX6.
> >
> > The docs for get_mbus_config [1] say:
> > @get_mbus_config: get the media bus configuration of a remote sub-device.
> > The media bus configuration is usually retrieved from the
> > firmware interface at sub-device probe time, immediately
> > applied to the hardware and eventually adjusted by the
> > driver.
> >
> > Currently, the imx-media-csi driver is not incorporating the information
> > from the firmware interface and therefore relies on the implementation of
> > get_mbus_config by the camera driver.
> >
> > To be compatible with camera drivers not implementing get_mbus_config
> > (which is the usual case), use the bus information from the fw interface:
> >
> > The camera does not necessarily has a direct media bus link to the CSI as
> > the video-mux and/or the MIPI CSI-2 receiver of the i.MX6 might be in
> > between them on the media pipeline.
> > The CSI driver already implements the functionality to find the connected
> > camera sub-device to call get_mbus_config on it.
> >
> > At this point the driver is modified as follows:
> > In the case that get_mbus_config is not implemented by the upstream
> > camera, try to get its endpoint configuration from the firmware interface
> > usign v4l2_fwnode_endpoint_parse.
> > For the supported mbus_types (V4L2_MBUS_PARALLEL, V4L2_MBUS_BT656 and
> > V4L2_MBUS_CSI2_DPHY), extract the mbus_config from the endpoint
> > configuration.
> > For all other mbus_types, return an error.
> >
> > Note that parsing the mbus_config from the fw interface is not done during
> > probing because the camera that's connected to the CSI can change based on
> > the selected input of the video-mux at runtime.
> >
> > [0] drivers/staging/media/imx/imx-media-csi.c - line 211..216
> > [1] include/media/v4l2-subdev.h - line 814
> >
> > Signed-off-by: Mathis Foerst <mathis.foerst@mt.com>
> > ---
> > drivers/staging/media/imx/imx-media-csi.c | 36 ++++++++++++++++++++---
> > 1 file changed, 32 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/staging/media/imx/imx-media-csi.c b/drivers/staging/media/imx/imx-media-csi.c
> > index 3edbc57be2ca..394a9321a10b 100644
> > --- a/drivers/staging/media/imx/imx-media-csi.c
> > +++ b/drivers/staging/media/imx/imx-media-csi.c
> > @@ -169,6 +169,8 @@ static int csi_get_upstream_mbus_config(struct csi_priv *priv,
> > {
> > struct v4l2_subdev *sd, *remote_sd;
> > struct media_pad *remote_pad;
> > + struct fwnode_handle *ep_node;
> > + struct v4l2_fwnode_endpoint ep = { .bus_type = 0 };
>
> Are there any defaults in DT bindings (other than 0's)? Also initialising a
> field to zero this way is redundant, just use {}.
>
I was going to respond in much the same way. This is equivalen to:
struct v4l2_fwnode_endpoint ep = { .bus_type = V4L2_MBUS_UNKNOWN };
> > int ret;
> >
> > if (!priv->src_sd)
> > @@ -210,11 +212,37 @@ static int csi_get_upstream_mbus_config(struct csi_priv *priv,
> >
> > ret = v4l2_subdev_call(remote_sd, pad, get_mbus_config,
> > remote_pad->index, mbus_cfg);
> > - if (ret == -ENOIOCTLCMD)
> > - v4l2_err(&priv->sd,
> > - "entity %s does not implement get_mbus_config()\n",
> > - remote_pad->entity->name);
> > + if (ret == -ENOIOCTLCMD) {
>
> if (!ret)
> return 0;
>
> And you can unindent the rest.
I was going to say this too but then I thought actually this needs to
be:
if (ret != -ENOIOCTLCMD)
return ret;
Which is weird. Better to break all the new code into a separate
helper function.
if (ret == -ENOIOCTLCMD)
ret = parse_fw_link_config_stuff();
return ret;
regards,
dan carpenter
next prev parent reply other threads:[~2025-03-06 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 11:38 [PATCH v1 0/1] " Mathis Foerst
2025-03-05 11:38 ` [PATCH v1 1/1] " Mathis Foerst
2025-03-06 16:33 ` Sakari Ailus
2025-03-06 19:07 ` Dan Carpenter [this message]
2025-03-06 21:13 ` Sakari Ailus
2025-03-07 13:38 ` Mathis Foerst
2025-03-10 10:25 ` Sakari Ailus
2025-03-14 15:26 ` Mathis Foerst
2025-03-14 15:48 ` Sakari Ailus
2025-03-21 15:28 ` Mathis Foerst
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=84aa2d87-d7f1-46c9-b28d-6f0e9a78788d@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manuel.traut@mt.com \
--cc=mathis.foerst@mt.com \
--cc=mathis.foerst@zuehlke.com \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=sakari.ailus@iki.fi \
--cc=shawnguo@kernel.org \
--cc=slongerbeam@gmail.com \
/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®