From: Herve Codina <herve.codina@bootlin.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
James Hilliard <james.hilliard1@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-gpio@vger.kernel.org, Bartosz Golaszewski <brgl@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexander Stein <linux@ew.tq-group.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: gpio: add gpio-aggregator binding
Date: Fri, 20 Feb 2026 14:07:03 +0100 [thread overview]
Message-ID: <20260220140703.0ba7b435@bootlin.com> (raw)
In-Reply-To: <CAMuHMdUkdF1X7xZvu9uhNPJBnq6grq-BvBk-598f=h7uTbYbVA@mail.gmail.com>
Hi,
On Fri, 20 Feb 2026 10:15:59 +0100
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> Hi Linus,
>
> On Fri, 20 Feb 2026 at 09:35, Linus Walleij <linusw@kernel.org> wrote:
> > On Fri, Feb 20, 2026 at 9:17 AM Herve Codina <herve.codina@bootlin.com> wrote:
> > > With nexus, you cannot translate &spi0.
> > >
> > > Also nexus works well when an index is involved. In other word, it works
> > > well with phandle with args.
> > >
> > > i2c-bus = <&i2c0>;
> > >
> > > In this kind of of definition, no index are present. With nexus node, this
> > > looks like
> > >
> > > i2c-bus = <&nexus>;
> > >
> > > How to handle multiple i2c busses with nexus node?
> >
> > Can't you just use the foo-n suffix trick from the pinctrl etc?
> >
> > my_nexus: nexus {
> > gpio-map = <...>;
> > interrupt-map = <...>;
> > nexus_i2c0: i2c-bus-0 = <&i2c4>;
> > nexus_i2c1: i2c-bus-1 = <&i2c6>;
> > nexus_i2c2: i2c-bus-3 = <&i2c8>;
> > };
> >
> > &nexus_i2c1 {
> > sensor@4c {
> > ....
> > };
> > };
> >
> > Maybe it's not as elegant but I think it could work?
>
> Wasn't that already solved using i2c-parent, cfr. the connectors
> discussion at last ELC-E?
Well, I wouldn't say "solved".
But yeah, the idea is i2c bus extension:
https://lore.kernel.org/all/20250205173918.600037-1-herve.codina@bootlin.com/
https://lore.kernel.org/all/20250618082313.549140-1-herve.codina@bootlin.com/
When DT overlays enter in the loop, the main issue is to reference a
symbol from the overlay.
This issue led to DT addons to replace overlays:
https://lore.kernel.org/all/de02ed8c-0176-4996-ad7a-680a2e115161@beagleboard.org/
All of these is really out of scope of this "dt-bindings: gpio: add
gpio-aggregator binding" series.
I am open to discuss nexus nodes, busses, DT addons but I don't thing this
series is the right place to do this discussions and, on my side, I don't
want to pollute James' work with all that stuff.
Best regards,
Hervé
next prev parent reply other threads:[~2026-02-20 13:07 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 8:13 [PATCH v2 1/2] dt-bindings: gpio: add gpio-aggregator binding James Hilliard
2026-02-11 8:13 ` [PATCH v2 2/2] gpio: aggregator: add gpio-aggregator DT compatible James Hilliard
2026-02-11 9:47 ` Bartosz Golaszewski
2026-02-11 9:50 ` Geert Uytterhoeven
2026-02-11 10:38 ` Bartosz Golaszewski
2026-02-11 10:48 ` Krzysztof Kozlowski
2026-02-11 11:00 ` Bartosz Golaszewski
2026-02-11 10:13 ` Krzysztof Kozlowski
2026-02-11 10:36 ` Bartosz Golaszewski
2026-02-11 10:42 ` Krzysztof Kozlowski
2026-02-11 10:44 ` Krzysztof Kozlowski
2026-02-11 21:47 ` Rob Herring
2026-02-11 21:49 ` James Hilliard
2026-02-12 7:18 ` Krzysztof Kozlowski
2026-02-12 19:16 ` James Hilliard
2026-02-13 7:31 ` Krzysztof Kozlowski
2026-02-13 8:02 ` James Hilliard
2026-02-13 8:21 ` Krzysztof Kozlowski
2026-02-13 8:29 ` Herve Codina
2026-02-13 8:49 ` Krzysztof Kozlowski
2026-02-13 23:03 ` James Hilliard
2026-02-11 8:17 ` [PATCH v2 1/2] dt-bindings: gpio: add gpio-aggregator binding Krzysztof Kozlowski
2026-02-11 8:19 ` Krzysztof Kozlowski
2026-02-11 8:28 ` James Hilliard
2026-02-11 8:44 ` Krzysztof Kozlowski
2026-02-11 17:01 ` James Hilliard
2026-02-12 14:49 ` Geert Uytterhoeven
2026-02-12 16:53 ` James Hilliard
2026-02-12 19:54 ` Rob Herring
2026-02-12 21:22 ` James Hilliard
2026-02-13 8:24 ` Geert Uytterhoeven
2026-02-13 18:34 ` James Hilliard
2026-02-16 9:05 ` Geert Uytterhoeven
2026-02-19 18:00 ` Linus Walleij
2026-02-19 18:29 ` Rob Herring
2026-02-19 22:14 ` Linus Walleij
2026-02-19 22:28 ` James Hilliard
2026-02-19 23:00 ` Linus Walleij
2026-02-19 23:06 ` James Hilliard
2026-02-19 23:12 ` Rob Herring
2026-02-20 4:57 ` James Hilliard
2026-02-20 8:24 ` Linus Walleij
2026-02-20 11:33 ` Bartosz Golaszewski
2026-02-13 14:34 ` Rob Herring
2026-02-13 22:49 ` James Hilliard
2026-02-16 9:10 ` Geert Uytterhoeven
2026-02-19 17:57 ` Linus Walleij
2026-02-20 8:17 ` Herve Codina
2026-02-20 8:35 ` Linus Walleij
2026-02-20 9:15 ` Geert Uytterhoeven
2026-02-20 13:07 ` Herve Codina [this message]
2026-02-20 13:28 ` Geert Uytterhoeven
2026-02-11 8:25 ` Geert Uytterhoeven
2026-02-11 8:34 ` James Hilliard
2026-02-11 9:47 ` Geert Uytterhoeven
2026-02-11 9:57 ` Herve Codina
2026-02-11 10:01 ` Geert Uytterhoeven
2026-02-11 10:58 ` Herve Codina
2026-02-11 13:30 ` Geert Uytterhoeven
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=20260220140703.0ba7b435@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=james.hilliard1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--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