From: David Gibson <david@gibson.dropbear.id.au>
To: Ayush Singh <ayush@beagleboard.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Herve Codina <herve.codina@bootlin.com>,
Andrew Davis <afd@ti.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Saravana Kannan <saravanak@google.com>,
devicetree@vger.kernel.org, devicetree-compiler@vger.kernel.org,
linux-kernel@vger.kernel.org,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v2 1/7] dt-bindings: Add support for export-symbols node
Date: Mon, 8 Sep 2025 14:48:25 +1000 [thread overview]
Message-ID: <aL5gGRlnbVuAQk-t@zatzit> (raw)
In-Reply-To: <ef7720ae-bada-4133-a685-d277cd4aa7e6@beagleboard.org>
[-- Attachment #1: Type: text/plain, Size: 4374 bytes --]
On Mon, Aug 18, 2025 at 11:07:57PM +0530, Ayush Singh wrote:
>
> On 8/18/25 22:35, Rob Herring wrote:
> > On Sun, Aug 17, 2025 at 3:42 AM Ayush Singh <ayush@beagleboard.org> wrote:
> > > On 8/17/25 13:52, Krzysztof Kozlowski wrote:
> > >
> > > > On 17/08/2025 10:18, Ayush Singh wrote:
> > > > > > > > Hardware:
> > > > > > > > i2c0 from SoC --------- connector 1, I2C A signals
> > > > > > > > i2c1 from SoC --------- connector 1, I2C B signals
> > > > > > > >
> > > > > > > > connector1 {
> > > > > > > > export-symbols {
> > > > > > > > i2c_a = <&i2c0>;
> > > > > > > > i2c_b = <&i2c1>;
> > > > > > > > };
> > > > > > > > };
> > > > > > > >
> > > > > > > > In order to avoid the coding style issue, this could be replace
> > > > > > > > with:
> > > > > > > > connector1 {
> > > > > > > > export-symbols {
> > > > > > > > symbol-names = "i2c_a", "i2c_b";
> > > > > > > > symbols = <&i2c0>, <&i2c1>;
> > > > > > > > };
> > > > > > > > };
> > > > > > > >
> > > > > > > > Krzysztof, Rob, do you think this could be accepted ?
> > > > > > > >
> > > > > > > > Ayush, David, do you thing this could be easily implemented in fdtoverlay ?
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Hervé
> > > > > > > >
> > > > > > > Well, it is possible.
> > > > > > >
> > > > > > > However, on connectors like pb2 header, there will be 50-100 export
> > > > > > > symbols. So it will start becoming difficult to maintain.
> > > > > > And the first syntax solves this how? I don't see the practical difference.
> > > > > Well, I was more worried about matching which phandle belongs to which
> > > > > symbol easily. Let us assume that 2 symbols will be in each line (after
> > > > > accounting for the indention and 80 char limit) and we have 70 symbols,
> > > > > so 35 lines. To check which phandle belongs to the 2nd symbol on line
> > > > > 25th line of symbol-names, well, you would at the best case need to
> > > > > have something like relative line numbers in your editor. Then you know
> > > > > that the 35th line from the current one is where you need to look.
> > > > >
> > > > > In the current syntax, the symbol name and phandle are on the same line.
> > > > > So well, easy to see which symbols refers to which phandle.
> > > > OK, that's valid point. Any ideas how to solve it without introducing
> > > > underscores for properties?
> > > >
> > > > Best regards,
> > > > Krzysztof
> > >
> > > Well, we can modify `get_phandle_from_symbols_node` to allow matching
> > > `*_*` to `*-*`. And we can do the same in devicetree easily enough. Not
> > > sure if implicit loose matching like that are the best idea.
> > >
> > > Zephyr does something similar for compatible strings. It pretty much
> > > replaces the all non alphanumeric characters with `_` in compatible
> > > string match. Although that is more to do with the limitation they are
> > > working with, i.e. the devicetree being converted to static headers
> > > instead of being runtime thing.
> > This is just going from bad to worse... If there's a real need to use
> > underscores, then use underscores. But that's all beside the point. I
> > didn't like v1 and nothing has changed in v2 to change that.
> >
> > This looks like continuing down the path of working around DTB format
> > limitations like DT overlays originally did (which both David (IIRC)
> > and I think was a mistake). But now instead of somewhat hidden,
> > generated data, you're adding manually written/maintained data. I
> > don't have any suggestion currently how to avoid that other than we
> > need to rev the DTB format which no one really wants to hear. Maybe
> > there's some other solution, but I don't have one ATM.
> >
> > Rob
>
> Well, if anyone decides to do a v2 of DTB, I would love to help in any way I
> can.
We're already on v17 of DTB (although only 5 of those version numbers
were actually used).
It shouldn't actually be that hard to extend it in a number of ways
without having to completely redefine it.
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-09-08 4:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 12:51 [PATCH v2 0/7] of: overlay: Add support for export-symbols node feature Herve Codina
2025-04-30 12:51 ` [PATCH v2 1/7] dt-bindings: Add support for export-symbols node Herve Codina
2025-05-02 14:33 ` Luca Ceresoli
2025-05-27 18:31 ` Krzysztof Kozlowski
2025-05-28 7:59 ` Ayush Singh
2025-05-28 8:06 ` Krzysztof Kozlowski
2025-05-28 16:57 ` Herve Codina
2025-06-04 18:35 ` Krzysztof Kozlowski
2025-06-18 9:32 ` Herve Codina
2025-06-18 9:54 ` Ayush Singh
2025-07-04 9:10 ` Herve Codina
2025-08-17 7:41 ` Krzysztof Kozlowski
2025-08-17 8:18 ` Ayush Singh
2025-08-17 8:22 ` Krzysztof Kozlowski
2025-08-17 8:42 ` Ayush Singh
2025-08-18 17:05 ` Rob Herring
2025-08-18 17:37 ` Ayush Singh
2025-09-08 4:48 ` David Gibson [this message]
2025-09-08 4:46 ` David Gibson
2025-09-08 4:44 ` David Gibson
2025-08-17 7:38 ` Krzysztof Kozlowski
2025-04-30 12:51 ` [PATCH v2 2/7] of: resolver: Introduce get_phandle_from_symbols_node() Herve Codina
2025-04-30 12:51 ` [PATCH v2 3/7] of: resolver: Add export_symbols in of_resolve_phandles() parameters Herve Codina
2025-05-02 14:35 ` Luca Ceresoli
2025-05-05 8:10 ` Herve Codina
2025-04-30 12:51 ` [PATCH v2 4/7] of: resolver: Add support for the export symbols node Herve Codina
2025-04-30 12:51 ` [PATCH v2 5/7] of: overlay: Add export_symbols_name in of_overlay_fdt_apply() parameters Herve Codina
2025-05-02 14:40 ` Ayush Singh
2025-05-05 8:17 ` Herve Codina
2025-04-30 12:51 ` [PATCH v2 6/7] of: overlay: Add support for the export symbols node Herve Codina
2025-04-30 12:51 ` [PATCH v2 7/7] of: unittest: Add tests for export symbols Herve Codina
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=aL5gGRlnbVuAQk-t@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=afd@ti.com \
--cc=arnd@arndb.de \
--cc=ayush@beagleboard.org \
--cc=conor+dt@kernel.org \
--cc=devicetree-compiler@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=herve.codina@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=thomas.petazzoni@bootlin.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