[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aLGHvqY6N5oI54eT@shikoro>
Date: Fri, 29 Aug 2025 12:58:06 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Herve Codina <herve.codina@...tlin.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 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?
All the best,
Wolfram
Powered by blists - more mailing lists