linux-kernel - Re: [PATCH v2 2/2] gpio: aggregator: add gpio-aggregator DT compatible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMuHMdWS-ZaL1nLS=C=hjBVJeVtgNYX-XgWf-8Oy4cGt6OMGDg@mail.gmail.com>
Date: Wed, 11 Feb 2026 10:50:19 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Bartosz Golaszewski <brgl@...nel.org>
Cc: James Hilliard <james.hilliard1@...il.com>, linux-gpio@...r.kernel.org, 
	Linus Walleij <linusw@...nel.org>, Rob Herring <robh@...nel.org>, 
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, 
	Alexander Stein <linux@...tq-group.com>, devicetree@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] gpio: aggregator: add gpio-aggregator DT compatible

Hi Bartosz,

On Wed, 11 Feb 2026 at 10:47, Bartosz Golaszewski <brgl@...nel.org> wrote:
> On Wed, Feb 11, 2026 at 9:14 AM James Hilliard
> <james.hilliard1@...il.com> wrote:
> >
> > Add an OF match entry for "gpio-aggregator" to support plain GPIO
> > forwarding from devicetree without delay semantics.
> >
> > This allows exposing selected lines as a logical GPIO controller with
> > stable aggregated offsets, so consumers can reference forwarded lines
> > instead of physical controller offsets. It also allows creating bundled
> > groups of named lines that can be exposed to userspace as a convenient
> > virtual gpiochip interface. Using "gpio-delay" for this case is not
> > suitable because it enables delay features and requires 3-cell GPIO
> > specifiers.
> >
> > Signed-off-by: James Hilliard <james.hilliard1@...il.com>

> > --- a/drivers/gpio/gpio-aggregator.c
> > +++ b/drivers/gpio/gpio-aggregator.c
> > @@ -1635,6 +1635,9 @@ static int gpio_aggregator_probe(struct platform_device *pdev)
> >  }
> >
> >  static const struct of_device_id gpio_aggregator_dt_ids[] = {
> > +       {
> > +               .compatible = "gpio-aggregator",
> > +       },
> >         {
> >                 .compatible = "gpio-delay",
> >                 .data = (void *)FWD_FEATURE_DELAY,
> > --
> > 2.43.0
> >
>
> Regardless of the DT bindings - this change is perfectly fine. We do
> that for other "virtual" devices like gpio-sim, gpio-virtuser, etc. I
> would just ask you to document it under
> Documentation/admin-guide/gpio/gpio-aggregator.rst.

This is not a pure virtual device, but for use with actual hardware.

Nacked-by: Geert Uytterhoeven <geert+renesas@...der.be>

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds