From: Conor Dooley <conor@kernel.org>
To: Alban Bedel <alban.bedel@lht.dlh.de>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: gpio: Add CAT9532 GPIO
Date: Tue, 15 Sep 2026 17:42:28 +0100 [thread overview]
Message-ID: <20260915-mystify-overvalue-89148836a662@spud> (raw)
In-Reply-To: <20260915092046.931449-2-alban.bedel@lht.dlh.de>
[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]
On Tue, Sep 15, 2026 at 11:20:45AM +0200, Alban Bedel wrote:
> Add devicetree binding document for CAT9532 LED dimmer as GPIO
> controller.
>
> Signed-off-by: Alban Bedel <alban.bedel@lht.dlh.de>
Some very interesting comments from Sashiko here, about whether this
should be handled in another subsystem.
At the very least, valid commentary from Linus.
pw-bot: changes-requested
Thanks,
Conor.
> ---
> .../bindings/gpio/onnn,cat9532.yaml | 52 +++++++++++++++++++
> 1 file changed, 52 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/gpio/onnn,cat9532.yaml
>
> diff --git a/Documentation/devicetree/bindings/gpio/onnn,cat9532.yaml b/Documentation/devicetree/bindings/gpio/onnn,cat9532.yaml
> new file mode 100644
> index 0000000000000..6f3e3d0f4f29b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/gpio/onnn,cat9532.yaml
> @@ -0,0 +1,52 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/gpio/onnn,cat9532.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: On Semiconductor CAT9532 LED dimmer as GPIO controller
> +
> +maintainers:
> + - Alban Bedel <alban.bedel@lht.dlh.de>
> +
> +properties:
> + compatible:
> + const: onnn,cat9532
> +
> + reg:
> + maxItems: 1
> +
> + gpio-controller: true
> +
> + "#gpio-cells":
> + const: 2
> +
> + ngpios:
> + minimum: 1
> + maximum: 16
> +
> +required:
> + - compatible
> + - reg
> + - gpio-controller
> + - "#gpio-cells"
> + - ngpios
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + gpio@60 {
> + compatible = "onnn,cat9532";
> + reg = <0x60>;
> +
> + gpio-controller;
> + #gpio-cells = <2>;
> +
> + ngpios = <16>;
> + };
> + };
> --
> 2.39.5
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-09-15 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 9:20 [PATCH 0/2] Support ON Semi CAT9532 Alban Bedel
2026-09-15 9:20 ` [PATCH 1/2] dt-bindings: gpio: Add CAT9532 GPIO Alban Bedel
2026-09-15 9:43 ` Linus Walleij
2026-09-15 9:47 ` Linus Walleij
2026-09-15 16:42 ` Conor Dooley [this message]
2026-09-15 9:20 ` [PATCH 2/2] gpio: Support ON Semi CAT9532 Alban Bedel
2026-09-15 9:51 ` Bartosz Golaszewski
2026-09-15 9:57 ` Bartosz Golaszewski
2026-09-15 13:48 ` Alban Bedel
2026-09-16 9:07 ` Bartosz Golaszewski
2026-09-15 9:59 ` Linus Walleij
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=20260915-mystify-overvalue-89148836a662@spud \
--to=conor@kernel.org \
--cc=alban.bedel@lht.dlh.de \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®