public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Petko Manolov <petko.manolov@konsulko.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, jacopo@jmondi.org
Subject: Re: hooking Sony 47MPixel sensor to NXP imx8m-mini MIPI CSI2
Date: Tue, 5 Jul 2022 15:30:41 +0300	[thread overview]
Message-ID: <YsQu8XxEj2zKPsJG@p310.k.g> (raw)
In-Reply-To: <YsQHwUCLlombAj85@p310.k.g>

On 22-07-05 12:43:41, Petko Manolov wrote:
> On 22-06-30 22:42:57, Laurent Pinchart wrote:
> > On Thu, Jun 30, 2022 at 09:52:05PM +0300, Petko Manolov wrote:
> > > On 22-06-30 03:50:55, Laurent Pinchart wrote:
> > > > 
> > > > 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).
> > > 
> > > The 5.15 NXP kernel got released sometime in June, but the CSI capture 
> > > drivers are pretty much the same as in their older versions.  So sad...
> > > 
> > > Nevermind, i'll share any good news here as well as the imx492 driver code 
> > > as soon i am certain it can successfully stream in at least one mode.
> > > 
> > > BTW, the 'fec' section in Variscite's var-som-symphony DT is broken for 
> > > v5.18 (mainline) kernels. I am not certain whom should i send the patch.  
> > > Would that be Rob Herring or should i just use 'git blame' to identify the 
> > > victim? :)
> > 
> > scripts/get_maintainer.pl is your friend for that.
> 
> Done, sent a patch for review to lkml and Rob.

Still waiting for the storm to come... ;)

> Banged on var-som-symphony DT enough to get imx492 detected (on 5.19.0-rc4) by 
> its driver.  imx-mipi-csis also looks happy enough.  Both drivers finish their 
> probe() successfully.  However, i don't see /dev/video0, any ideas what might 
> be the reason?

Please ignore the above.  I had to enable VIDEO_IMX7_CSI for the right driver to 
get loaded.  What a mess.


		Petko

  reply	other threads:[~2022-07-05 12:55 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
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 [this message]
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=YsQu8XxEj2zKPsJG@p310.k.g \
    --to=petko.manolov@konsulko.com \
    --cc=jacopo@jmondi.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.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