From: Jai Luthra <jai.luthra@ideasonboard.com>
To: Dave Stevenson <dave.stevenson@raspberrypi.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Alexander Shiyan <eagle.alexander923@gmail.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/4] Update imx678 to act as a common Sony Starvis 2 driver.
Date: Thu, 03 Sep 2026 17:55:23 +0530 [thread overview]
Message-ID: <178843832369.11722.3418940142738960168@freya> (raw)
In-Reply-To: <CAPY8ntChzSsnbXcNi6rPhzWsrS-uL_odbVZoSpj0byFQnhYOZQ@mail.gmail.com>
Quoting Dave Stevenson (2026-09-03 17:25:42)
> Hi Jai
>
> Thanks for looking at the series.
>
> On Thu, 3 Sept 2026 at 05:13, Jai Luthra <jai.luthra@ideasonboard.com> wrote:
> >
> > Hi Dave,
> >
> > Thank you, I'm glad this turned out quite clean :-)
> >
> > Quoting Dave Stevenson (2026-08-05 21:39:15)
> > > The IMX678 (8MPix) driver has been accepted.
> > >
> > > Whilst preparing a patchset for IMX662 (1080p), I observed such
> > > commonality between the two that it seemed sensible to attempt
> > > a common driver rather than submitting a separate IMX662 series
> > > again.
> > >
> > > On checking my box of sensors, I found I had an IMX675 (5MPix) as
> > > well, so that has been incorporated.
> > >
> > > This set proposes a common driver that is working with all 3 of
> > > those sensors.
> > > It's sent as an RFC to gather confirmation that the resulting driver
> > > structure is acceptable as implied by [1].
> > >
> >
> > Overall structure looks good to me, I was able to stream with the Soho
> > IMX662 module I have.
> >
> > > If it is viewed as acceptable then there is still a modest amount
> > > of tidying up required:
> > > - DT binding updates for the extra compatibles.
> > > - Rename the common functions so that the model references are
> > > only on the model specific parts.
> > > - Add the Sony init sequence for IMX662.
> >
> > I added most of the registers I could see were different from the default
> > values:
> > https://github.com/jailuthra/linux/commit/9ecb2d905581e9cf7ca61aa45c3b440fe7042307
>
> I just hadn't had the time to analyse the Sony docs when I sent the
> first stab. I've now done so from their magic spreadsheet, so
> hopefully our values match.
>
> I've now got docs for all of them from Sony, so will check through them.
> And I've just been told IMX832 (new 2MPix) also matches this scheme,
> so that'll be another variant.
>
> If you're on board with this, I'll do a wholesale replacement of
> imx678 with starvis2 in common defines, function names, and the file
> to starvis2.c as a first patch?
>
Sounds good, thank you!
Jai
prev parent reply other threads:[~2026-09-03 12:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 16:09 Dave Stevenson
2026-08-05 16:09 ` [PATCH RFC 1/4] media: i2c: imx678: Always program the sensor in window mode Dave Stevenson
2026-09-03 4:16 ` Jai Luthra
2026-08-05 16:09 ` [PATCH RFC 2/4] media: i2c: imx678: Parameterise the configuration to allow for other models Dave Stevenson
2026-09-03 4:15 ` Jai Luthra
2026-08-05 16:09 ` [PATCH RFC 3/4] media: i2c: imx678: Add imx662 support to the driver Dave Stevenson
2026-09-03 4:20 ` Jai Luthra
2026-09-03 11:46 ` Dave Stevenson
2026-08-05 16:09 ` [PATCH RFC 4/4] media: i2c: imx678: Add imx675 " Dave Stevenson
2026-09-03 4:22 ` Jai Luthra
2026-09-03 11:54 ` Dave Stevenson
2026-09-03 12:24 ` Jai Luthra
2026-09-03 4:13 ` [PATCH RFC 0/4] Update imx678 to act as a common Sony Starvis 2 driver Jai Luthra
2026-09-03 11:55 ` Dave Stevenson
2026-09-03 12:25 ` Jai Luthra [this message]
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=178843832369.11722.3418940142738960168@freya \
--to=jai.luthra@ideasonboard.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=eagle.alexander923@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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®