public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bartosz Golaszewski <brgl@kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: James Hilliard <james.hilliard1@gmail.com>,
	linux-gpio@vger.kernel.org, Linus Walleij <linusw@kernel.org>,
	Rob Herring <robh@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 2/2] gpio: aggregator: add gpio-aggregator DT compatible
Date: Wed, 11 Feb 2026 11:48:59 +0100	[thread overview]
Message-ID: <2c5734db-1e62-4aeb-9c6a-ef14939575c2@kernel.org> (raw)
In-Reply-To: <CAMRc=MdRn=791YHaGZ7s+rwftJ84PYRivOO8gPPbCMNF6MUH3w@mail.gmail.com>

On 11/02/2026 11:38, Bartosz Golaszewski wrote:
> On Wed, Feb 11, 2026 at 10:50 AM Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>>
>>>>
>>>>  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@glider.be>
>>
> 
> Well, it is a virtual device in that there's no actual "aggregator"
> device on the board. It virtually aggregates GPIOs into a separate
> chip for user's convenience. While there's no such device as a
> gpio-aggregator - and so we must not put it into bindings nor into
> mainline devicetree sources - having a compatible matching in the
> driver is perfectly fine IMO. Just like gpio-sim.

I already wrote, you cannot have undocumented compatible. There are even
explicit checks for this - in schema and checkpatch - so with your
approach you accept known warnings. Really, no, and fact we need to keep
discussing it:

Nacked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

Best regards,
Krzysztof

  reply	other threads:[~2026-02-11 10:49 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 [this message]
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
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=2c5734db-1e62-4aeb-9c6a-ef14939575c2@kernel.org \
    --to=krzk@kernel.org \
    --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=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