From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Petko Manolov <petko.manolov@konsulko.com>
Cc: linux-media@vger.kernel.org, jacopo@jmondi.org
Subject: Re: hooking Sony 47MPixel sensor to NXP imx8m-mini MIPI CSI2
Date: Thu, 30 Jun 2022 03:50:55 +0300 [thread overview]
Message-ID: <YrzzbwYr+ztrXbgZ@pendragon.ideasonboard.com> (raw)
In-Reply-To: <YrwRROJbH/P5lYi+@carbon.lan>
Hi Petko,
On Wed, Jun 29, 2022 at 11:45:56AM +0300, Petko Manolov wrote:
> On 22-06-29 11:28:26, Laurent Pinchart wrote:
> > On Wed, Jun 29, 2022 at 10:55:43AM +0300, Petko Manolov wrote:
> > > Hi guys,
> > >
> > > First, i'd like to apologize for the noise and sending this email directly.
> >
> > Your support request is directed to the linux-media mailing list, CC'ing
> > appropriate developers is a good practice to make sure we notice, there's
> > nothing to apologize for.
>
> Well, it could still be annoyance.
>
> > > I am trying to hook Sony IMX492 sensor to v5.10 imx8m-mini based platform.
> > > The capture driver does not support Bayer GBRG 10 and 12bit pixel format, so
> > > i had to add these. I also stumbled upon a bug in mx6s_capture.c which, i
> > > assume, is completely out of interest here as it's related to a vendor tree.
> >
> > I'm surprised you stumbled upon one bug only :-) I always advise to stay away
> > from BSP code as much as possible.
>
> I am certain there is a bunch of these, but this particular one was hard not to
> notice immediately, being NULL pointer dereference. :)
>
> > > I got as far as sensor is registering with the capture mipi csi driver and,
> > > if HW is properly set up on both sides, should be streaming. While my
> > > confidence is pretty high about the IMX492 setup i can't say the same about
> > > the recipient part.
> > >
> > > So here is my question: how stable are NXP's MIPI CSI2 and CSI2 bridge
> > > drivers in v5.18? Would it be better to switch to this version instead of
> > > hacking madly at the v5.10 vendor code?
> >
> > I consider them more stable than the vendor code. If there are issues there,
> > we can help fixing them.
>
> I might be mistaken, but at least in terms of media drivers code in NXP's 5.18
> seems either pretty close to mainline or maybe the same. What's your advice,
> shall i use their (5.18.x+fslc) branch or take only the device-tree, if needed?
For an i.MX8MM I'd try running the mainline kernel directly. If that
doesn't work, I would backport the camera drivers from mainline to the
v5.15 NXP kernel. As far as I know, the v5.18 branch isn't an official
BSP release (I'm actually not sure what it's for).
> > > I've already published the code here. Once the development is done the
> > > intent is to mainline Sony IMX492 sensor driver.
> >
> > That's great ! I'm looking forward to that.
>
> Sure, that's the goal here.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2022-06-30 0:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 7:55 hooking Sony 47MPixel sensor to NXP imx8m-mini MIPI CSI2 Petko Manolov
2022-06-29 8:28 ` Laurent Pinchart
2022-06-29 8:45 ` Petko Manolov
2022-06-30 0:50 ` Laurent Pinchart [this message]
2022-06-30 18:52 ` Petko Manolov
2022-06-30 19:42 ` Laurent Pinchart
2022-07-05 9:43 ` Petko Manolov
2022-07-05 12:30 ` Petko Manolov
2022-07-05 14:42 ` Alexander Stein
2022-07-05 15:13 ` Petko Manolov
2022-07-06 6:18 ` Alexander Stein
2022-07-06 13:07 ` Petko Manolov
2022-07-06 13:12 ` Alexander Stein
2022-07-06 13:51 ` Laurent Pinchart
2022-07-06 19:26 ` Petko Manolov
2022-07-06 20:07 ` Petko Manolov
2022-07-06 21:48 ` Laurent Pinchart
2022-07-07 12:20 ` Petko Manolov
2022-07-06 21:47 ` Laurent Pinchart
2022-07-07 12:17 ` Petko Manolov
2022-07-07 21:47 ` Laurent Pinchart
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=YrzzbwYr+ztrXbgZ@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=jacopo@jmondi.org \
--cc=linux-media@vger.kernel.org \
--cc=petko.manolov@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.