From: Herve Codina <herve.codina@bootlin.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Rob Herring <robh@kernel.org>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Ayush Singh <ayush@beagleboard.org>,
Andi Shyti <andi.shyti@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree-spec@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v3 1/1] schemas: i2c: Introduce I2C bus extensions
Date: Fri, 29 Aug 2025 13:08:21 +0200 [thread overview]
Message-ID: <20250829130821.472a96dc@bootlin.com> (raw)
In-Reply-To: <aLGHvqY6N5oI54eT@shikoro>
Hi Wolfram,
On Fri, 29 Aug 2025 12:58:06 +0200
Wolfram Sang <wsa+renesas@sang-engineering.com> wrote:
> Hi Hervé,
>
> > the only solution I see is to parse the full DT in order to find extension
> > nodes when we need to register adapter children (adapter probe() step).
> >
> > A matching extension node will be a node where:
> > 1) compatible = "i2c-bus-extension"
> > 2) "i2c-parent" phandle points to the expected adapter.
>
> Would that be so bad? It will not be done often, or?
Ok I will propose a binding update in that sense (dtschema repo) and an
implementation (kernel repo).
Best regards,
Hervé
prev parent reply other threads:[~2025-08-29 11:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 8:23 [PATCH v3 0/1] i2c: Introduce I2C bus extensions Herve Codina
2025-06-18 8:23 ` [PATCH v3 1/1] schemas: " Herve Codina
2025-08-01 18:09 ` Rob Herring
2025-08-08 16:07 ` Luca Ceresoli
2025-08-08 20:51 ` Rob Herring
2025-08-26 14:03 ` Wolfram Sang
2025-08-29 10:52 ` Herve Codina
2025-08-29 10:58 ` Wolfram Sang
2025-08-29 11:08 ` Herve Codina [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=20250829130821.472a96dc@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=andi.shyti@kernel.org \
--cc=ayush@beagleboard.org \
--cc=conor+dt@kernel.org \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).