mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: "jacopo.mondi@ideasonboard.com" <jacopo.mondi@ideasonboard.com>,
	"laurent.pinchart@ideasonboard.com" 
	<laurent.pinchart@ideasonboard.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"slongerbeam@gmail.com" <slongerbeam@gmail.com>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	Aishwarya Kothari <aishwarya.kothari@toradex.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
	"mchehab@kernel.org" <mchehab@kernel.org>,
	"sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>
Subject: Re: [PATCH v1] media: i2c: ov5640: Implement get_mbus_config
Date: Sat, 28 Jan 2023 11:36:49 +0000	[thread overview]
Message-ID: <b851143625401cac631b099e1b496bc726e19e4d.camel@toradex.com> (raw)
In-Reply-To: <Y9QZH2/jDbFbew2D@pendragon.ideasonboard.com>

Hi Laurent

On Fri, 2023-01-27 at 20:34 +0200, Laurent Pinchart wrote:
> 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.

Remember, this is on Apalis iMX6 where we do and always did specify the lanes on both sides of the link ([1],
[2]) or are we missing anything else in that respect?

Fact is, that with this patch (and the two from Hans [3], [4]) all starts working again. So it really seems
required.

[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/imx6qdl-apalis.dtsi#n710
[2]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/imx6qdl-apalis.dtsi#n755
[3] https://lore.kernel.org/all/69624c54-7cbd-7362-c468-f8ffea9614be@xs4all.nl/
[4] https://lore.kernel.org/all/c12cfcc5-1d46-7b5f-4a27-f4cd52a1b885@xs4all.nl/

Cheers

Marcel

> > > 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 = {

  parent reply	other threads:[~2023-01-28 11:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 15:12 Marcel Ziswiler
2023-01-27 17:50 ` Jacopo Mondi
2023-01-27 18:34   ` Laurent Pinchart
2023-01-28 10:06     ` Jacopo Mondi
2023-01-30  9:24       ` Philipp Zabel
2023-01-28 11:36     ` Marcel Ziswiler [this message]
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=b851143625401cac631b099e1b496bc726e19e4d.camel@toradex.com \
    --to=marcel.ziswiler@toradex.com \
    --cc=aishwarya.kothari@toradex.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=kernel@pengutronix.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®