From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Petko Manolov <petko.manolov@konsulko.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org, jacopo@jmondi.org
Subject: Re: Re: hooking Sony 47MPixel sensor to NXP imx8m-mini MIPI CSI2
Date: Tue, 05 Jul 2022 16:42:16 +0200 [thread overview]
Message-ID: <12352558.O9o76ZdvQC@steina-w> (raw)
In-Reply-To: <YsQHwUCLlombAj85@p310.k.g>
Hi Petko,
Am Dienstag, 5. Juli 2022, 11:43:29 CEST schrieb Petko Manolov:
> 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.
Do you have a link for the mailing list archive? I failed to find the patch. I
just want to check how things are done compared to other sensors.
Best reagrds,
Alexander
next prev parent reply other threads:[~2022-07-05 14:42 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
2022-07-05 14:42 ` Alexander Stein [this message]
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=12352558.O9o76ZdvQC@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=jacopo@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox