Re: [PATCH RFC 1/2] dt-bindings: regmap: add common schema for no-sequential-read

Mark Brown <[email protected]> Wed, 22 Jul 2026 21:20:48 +0100

Newsgroups	dev.linux.lists.driver-core,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel
Message-ID	<[email protected]>

On Wed, Jul 22, 2026 at 08:24:37PM +0200, Richard Leitner wrote:
> On Wed, Jul 22, 2026 at 02:59:12PM +0100, Mark Brown wrote:

> > No, this should not be a DT property.  We should discover this through
> > the bus, just like we do currently for the various I2C quirks that are
> > advertied by the I2C subsystem.

> What do you mean "discover this through the bus"? As mentioned in the
> commit message there is no possibility to detect that within the affected
> I2C device drivers.

> Or do you mean that it should be "discovered" by modelling the MCU which
> "proxies" the I2C traffic between the host and the sensor/device as some
> kind of "parent" device of the sensor?

If there is hardware there that rewrites the traffic then obviously that
hardware should be described in the device tree, yes.  It sounds like
this is the actual I2C controller and is what is imposing the limits.

signature.asc (application/pgp-signature, 488 B)