From: Richard Leitner <richard.leitner@linux.dev>
To: Mark Brown <broonie@kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
driver-core@lists.linux.dev
Subject: Re: [PATCH RFC 1/2] dt-bindings: regmap: add common schema for no-sequential-read
Date: Thu, 23 Jul 2026 13:01:11 +0200 [thread overview]
Message-ID: <amHznORUaOnUFyS4@bombadil> (raw)
In-Reply-To: <525338f4-cad3-4acb-94c5-a4b71cde9c02@sirena.org.uk>
On Wed, Jul 22, 2026 at 11:03:09PM +0100, Mark Brown wrote:
> On Wed, Jul 22, 2026 at 11:58:46PM +0200, Richard Leitner wrote:
>
> > @Mark: I understood that if the fpga really intercepts the I2C bus, it
> > should be modelled accordingly in device tree. But what would be the
> > preferred implementation if both devices sit on the same I2C bus, but
> > one is messing up some register reads on purpose?
>
> I think we would need to have a coherent understanding and description
> of the actual issue to know how to describe it.
Understood. I will try to figure out how the hardware is really wired
and come back to you.
>
> Please do not add random characters to my name.
Sorry, I didn’t mean any harm.
next prev parent reply other threads:[~2026-07-23 11:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 8:42 [PATCH RFC 0/2] regmap: support firmware-described non-sequential register reads Richard Leitner
2026-07-22 8:42 ` [PATCH RFC 1/2] dt-bindings: regmap: add common schema for no-sequential-read Richard Leitner
2026-07-22 13:59 ` Mark Brown
2026-07-22 18:24 ` Richard Leitner
2026-07-22 20:16 ` Laurent Pinchart
2026-07-22 21:58 ` Richard Leitner
2026-07-22 22:03 ` Mark Brown
2026-07-23 11:01 ` Richard Leitner [this message]
2026-07-23 15:45 ` Laurent Pinchart
2026-07-23 16:02 ` Conor Dooley
2026-07-23 16:10 ` Laurent Pinchart
2026-07-23 16:31 ` Conor Dooley
2026-07-23 16:38 ` Laurent Pinchart
2026-07-23 18:55 ` Richard Leitner
2026-07-24 9:28 ` Laurent Pinchart
2026-07-22 20:20 ` Mark Brown
2026-07-22 8:42 ` [PATCH RFC 2/2] regmap: implement no-sequential-read firmware property 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=amHznORUaOnUFyS4@bombadil \
--to=richard.leitner@linux.dev \
--cc=alexander.stein@ew.tq-group.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dakr@kernel.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=devicetree@vger.kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
/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