All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	Richard Leitner <richard.leitner@linux.dev>,
	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:12:21 +0300	[thread overview]
Message-ID: <20260721151221.GM50424@killaraus.ideasonboard.com> (raw)
In-Reply-To: <2422477.ElGaqSPkdT@steina-w>

On Tue, Jul 21, 2026 at 03:38:26PM +0200, Alexander Stein wrote:
> Hi Richard,
> 
> thanks for addressing this long-standing issue.
> 
> Am Dienstag, 21. Juli 2026, 15:25:29 CEST schrieb Richard Leitner:
> > 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.
> > 
> > As the driver has no reliable way to identify affected modules enable
> > use_single_read for OV9282 unconditionally when creating the CCI regmap.
> 
> What about a property in the DT instead? In DT it should be clear if a
> Vision Components camera is used.

Yes, this should not be done by default, or we'll have to do the same
for all sensors used in any module from Vision Components.

> > Tested on an i.M8MP system with OV9282 modules from Vision Components.
> > 
> > Signed-off-by: Richard Leitner <richard.leitner@linux.dev>
> > ---
> >  drivers/media/i2c/ov9282.c | 7 ++++++-
> >  1 file changed, 6 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/media/i2c/ov9282.c b/drivers/media/i2c/ov9282.c
> > index 5b6f897a74fcd..8267a0a9c6f2d 100644
> > --- a/drivers/media/i2c/ov9282.c
> > +++ b/drivers/media/i2c/ov9282.c
> > @@ -1283,6 +1283,11 @@ static int ov9282_probe(struct i2c_client *client)
> >  	struct ov9282 *ov9282;
> >  	int ret;
> >  
> > +	const struct cci_regmap_config config = {
> > +		.reg_addr_bits = 16,
> > +		.use_single_read = true,
> > +	};
> > +
> >  	ov9282 = devm_kzalloc(&client->dev, sizeof(*ov9282), GFP_KERNEL);
> >  	if (!ov9282)
> >  		return -ENOMEM;
> > @@ -1301,7 +1306,7 @@ static int ov9282_probe(struct i2c_client *client)
> >  		return ret;
> >  	}
> >  
> > -	ov9282->regmap = devm_cci_regmap_init_i2c(client, 16);
> > +	ov9282->regmap = devm_cci_regmap_init_i2c_cfg(client, &config);
> >  	if (IS_ERR(ov9282->regmap))
> >  		return dev_err_probe(ov9282->dev, PTR_ERR(ov9282->regmap),
> >  				     "Failed to init CCI\n");

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2026-07-21 15:12 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 single-read I2C transactions 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 [this message]
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

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=20260721151221.GM50424@killaraus.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=richard.leitner@linux.dev \
    --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 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.