[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250829130821.472a96dc@bootlin.com>
Date: Fri, 29 Aug 2025 13:08:21 +0200
From: Herve Codina <herve.codina@...tlin.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc: Rob Herring <robh@...nel.org>, Luca Ceresoli
<luca.ceresoli@...tlin.com>, Ayush Singh <ayush@...gleboard.org>, Andi
Shyti <andi.shyti@...nel.org>, Krzysztof Kozlowski <krzk@...nel.org>, Conor
Dooley <conor+dt@...nel.org>, linux-i2c@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree-spec@...r.kernel.org, Thomas Petazzoni
<thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH v3 1/1] schemas: i2c: Introduce I2C bus extensions
Hi Wolfram,
On Fri, 29 Aug 2025 12:58:06 +0200
Wolfram Sang <wsa+renesas@...g-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é
Powered by blists - more mailing lists