From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: Marcel Ziswiler <marcel@ziswiler.com>,
linux-media@vger.kernel.org, kernel@pengutronix.de,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Aishwarya Kothari <aishwarya.kothari@toradex.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Steve Longerbeam <slongerbeam@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] media: i2c: ov5640: Implement get_mbus_config
Date: Fri, 27 Jan 2023 20:34:07 +0200 [thread overview]
Message-ID: <Y9QZH2/jDbFbew2D@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20230127175003.6ofmfaqovbqu54hg@uno.localdomain>
On Fri, Jan 27, 2023 at 06:50:03PM +0100, Jacopo Mondi wrote:
> On Fri, Jan 27, 2023 at 04:12:44PM +0100, Marcel Ziswiler wrote:
> > From: Aishwarya Kothari <aishwarya.kothari@toradex.com>
> >
> > Implement the introduced get_mbus_config operation to report the
> > number of used data lanes on the MIPI CSI-2 interface.
> >
>
> OV5640 can operate in parallel mode too.
>
> You can check how it currently configured with ov5640_is_csi2() and
> populate struct v4l2_mbus_config accordingly.
I'm also wondering which CSI-2 receiver needs .get_mbus_config() for the
ov5640. The number of lanes is usually specified in DT, on both sides of
the link. It's only when selecting a number of lanes dynamically at
runtime that .get_mbus_config() is needed.
> > Signed-off-by: Aishwarya Kothari <aishwarya.kothari@toradex.com>
> > Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> >
> > ---
> >
> > drivers/media/i2c/ov5640.c | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> >
> > diff --git a/drivers/media/i2c/ov5640.c b/drivers/media/i2c/ov5640.c
> > index e0f908af581b..42d43f0d1e1c 100644
> > --- a/drivers/media/i2c/ov5640.c
> > +++ b/drivers/media/i2c/ov5640.c
> > @@ -3733,6 +3733,19 @@ static int ov5640_init_cfg(struct v4l2_subdev *sd,
> > return 0;
> > }
> >
> > +static int ov5640_get_mbus_config(struct v4l2_subdev *sd,
> > + unsigned int pad,
> > + struct v4l2_mbus_config *cfg)
> > +{
> > + struct ov5640_dev *sensor = to_ov5640_dev(sd);
> > +
> > + cfg->type = V4L2_MBUS_CSI2_DPHY;
> > + cfg->bus.mipi_csi2.num_data_lanes = sensor->ep.bus.mipi_csi2.num_data_lanes;
> > + cfg->bus.mipi_csi2.flags = 0;
> > +
> > + return 0;
> > +}
> > +
> > static const struct v4l2_subdev_core_ops ov5640_core_ops = {
> > .log_status = v4l2_ctrl_subdev_log_status,
> > .subscribe_event = v4l2_ctrl_subdev_subscribe_event,
> > @@ -3753,6 +3766,7 @@ static const struct v4l2_subdev_pad_ops ov5640_pad_ops = {
> > .get_selection = ov5640_get_selection,
> > .enum_frame_size = ov5640_enum_frame_size,
> > .enum_frame_interval = ov5640_enum_frame_interval,
> > + .get_mbus_config = ov5640_get_mbus_config,
> > };
> >
> > static const struct v4l2_subdev_ops ov5640_subdev_ops = {
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-01-27 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 15:12 [PATCH v1] media: i2c: ov5640: Implement get_mbus_config Marcel Ziswiler
2023-01-27 17:50 ` Jacopo Mondi
2023-01-27 18:34 ` Laurent Pinchart [this message]
2023-01-28 10:06 ` Jacopo Mondi
2023-01-30 9:24 ` Philipp Zabel
2023-01-28 11:36 ` Marcel Ziswiler
2023-01-28 8:31 ` Marcel Ziswiler
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=Y9QZH2/jDbFbew2D@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=aishwarya.kothari@toradex.com \
--cc=francesco.dolcini@toradex.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=marcel@ziswiler.com \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=sakari.ailus@linux.intel.com \
--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