From: Richard Leitner <richard.leitner@linux.dev>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Dave Stevenson <dave.stevenson@raspberrypi.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Hans de Goede <hansg@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] media: ov9282: enable single-read I2C transactions
Date: Tue, 21 Jul 2026 18:01:10 +0200 [thread overview]
Message-ID: <al-XSDYrEfMmaEqR@bombadil> (raw)
In-Reply-To: <20260721155822.GB536385@killaraus.ideasonboard.com>
On Tue, Jul 21, 2026 at 06:58:22PM +0300, Laurent Pinchart wrote:
> On Tue, Jul 21, 2026 at 05:44:21PM +0200, Richard Leitner wrote:
> > Hi Laurent,
> >
> > thank you very much for your quick feedback!
> >
> > On Tue, Jul 21, 2026 at 06:16:14PM +0300, Laurent Pinchart wrote:
> > > On Tue, Jul 21, 2026 at 02:39:46PM +0100, Dave Stevenson wrote:
> > > > On Tue, 21 Jul 2026 at 14:25, Richard Leitner wrote:
> > > > >
> > > > > Some OV9282 camera modules, such as those from Vision Components, fail
> > > > > multi-byte register reads with the default CCI I2C regmap access pattern
> > > > > and only work when single-register read transactions are used. This
> > > > > results in the driver being unable to probe due to a chip id mismatch.
> > > >
> > > > Those damn stupid Vision Components modules with the MCU that prevents
> > > > you reading registers.
> > >
> > > There's good news, the situation is improving with recent modules. We
> > > still have to handle the other ones of course.
> > >
> > > > I seem to recall Laurent had a plan for how to handle those without
> > > > having to patch all the drivers, however I can't find that thread
> > > > quickly.
> > >
> > > I'm thinking of two options:
> > >
> > > - We can introduce a new standard DT property for I2C device that will
> > > be parsed by regmap or the I2C core directly, and switch to single
> > > reads.
> > >
> > > - We could model the MCU as some sort of I2C mux, sitting in DT between
> > > the I2C controller and the image sensor, and translate multi-byte
> > > reads to single-byte reads in that driver.
> >
> > I'm basically fine with both. Personally I would prefer the first
> > option, as this would be a generic approach which other devices could also
> > use. Furthermore it's IMHO the simpler solution. But that's just my 2 cents.
>
> The next step is to then write and send an RFC, to get feedback on the
> idea from the DT and I2C maintainers (and possibly regmap, if we handle
> the quirk at that level). Is that something you could work on ?
Sure. I'll take a more detailled look at it tomorrow.
regards;rl
...
> --
> Regards,
>
> Laurent Pinchart
prev parent reply other threads:[~2026-07-21 16:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 13:25 [PATCH 0/2] media: v4l2-cci/ov9282: support " Richard Leitner
2026-07-21 13:25 ` [PATCH 1/2] media: v4l2-cci: Add support for custom regmap configuration Richard Leitner
2026-07-21 13:25 ` [PATCH 2/2] media: ov9282: enable single-read I2C transactions Richard Leitner
2026-07-21 13:38 ` Alexander Stein
2026-07-21 15:12 ` Laurent Pinchart
2026-07-21 15:15 ` Richard Leitner
2026-07-21 15:32 ` Laurent Pinchart
2026-07-21 15:57 ` Richard Leitner
2026-07-22 8:00 ` Alexander Stein
2026-07-21 13:39 ` Dave Stevenson
2026-07-21 15:16 ` Laurent Pinchart
2026-07-21 15:44 ` Richard Leitner
2026-07-21 15:58 ` Laurent Pinchart
2026-07-21 16:01 ` Richard Leitner [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=al-XSDYrEfMmaEqR@bombadil \
--to=richard.leitner@linux.dev \
--cc=dave.stevenson@raspberrypi.com \
--cc=hansg@kernel.org \
--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®