From: Tzuyi Chang <tychang@realtek.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andy@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <linux-gpio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, TY Chang <tychang@realtek.com>
Subject: [PATCH 2/2] dt-bindings: gpio: realtek: Add realtek,rtd-gpio bindings
Date: Wed, 1 Nov 2023 10:58:02 +0800 [thread overview]
Message-ID: <20231101025802.3744-3-tychang@realtek.com> (raw)
In-Reply-To: <20231101025802.3744-1-tychang@realtek.com>
This patch adds the device tree bindings for the Realtek DHC RTD SoCs
GPIO controllers.
Signed-off-by: Tzuyi Chang <tychang@realtek.com>
---
.../bindings/gpio/realtek,rtd-gpio.yaml | 56 +++++++++++++++++++
1 file changed, 56 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/realtek,rtd-gpio.yaml
diff --git a/Documentation/devicetree/bindings/gpio/realtek,rtd-gpio.yaml b/Documentation/devicetree/bindings/gpio/realtek,rtd-gpio.yaml
new file mode 100644
index 000000000000..6cab7ec50c88
--- /dev/null
+++ b/Documentation/devicetree/bindings/gpio/realtek,rtd-gpio.yaml
@@ -0,0 +1,56 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+# Copyright 2023 Realtek Semiconductor Corporation
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/gpio/realtek,rtd-gpio.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Realtek DHC GPIO controller
+
+maintainers:
+ - TY Chang <tychang@realtek.com>
+
+properties:
+ compatible:
+ enum:
+ - realtek,rtd-gpio
+ - realtek,rtd1295-misc-gpio
+ - realtek,rtd1295-iso-gpio
+ - realtek,rtd1395-iso-gpio
+ - realtek,rtd1619-iso-gpio
+
+ reg:
+ maxItems: 2
+
+ interrupts:
+ maxItems: 2
+
+ gpio-ranges: true
+
+ gpio-controller: true
+
+ "#gpio-cells":
+ const: 2
+
+required:
+ - compatible
+ - reg
+ - interrupts
+ - gpio-ranges
+ - gpio-controller
+ - "#gpio-cells"
+
+additionalProperties: false
+
+examples:
+ - |
+ gpio@100 {
+ compatible = "realtek,rtd-gpio";
+ reg = <0x100 0x100>,
+ <0x000 0x0b0>;
+ interrupt-parent = <&iso_irq_mux>;
+ interrupts = <19>, <20>;
+ gpio-ranges = <&pinctrl 0 0 82>;
+ gpio-controller;
+ #gpio-cells = <2>;
+ };
--
2.42.0
next prev parent reply other threads:[~2023-11-01 2:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 2:58 [PATCH 0/2] Add gpio driver support for Realtek DHC SoCs Tzuyi Chang
2023-11-01 2:58 ` [PATCH 1/2] gpio: realtek: Add GPIO support for RTD SoC variants Tzuyi Chang
2023-11-01 7:15 ` Krzysztof Kozlowski
2023-11-02 3:30 ` TY_Chang[張子逸]
2023-11-02 7:11 ` Krzysztof Kozlowski
2023-11-03 9:09 ` TY_Chang[張子逸]
2023-11-01 8:39 ` Linus Walleij
2023-11-02 12:40 ` TY_Chang[張子逸]
2023-11-02 14:52 ` Linus Walleij
2023-11-01 2:58 ` Tzuyi Chang [this message]
2023-11-01 7:13 ` [PATCH 2/2] dt-bindings: gpio: realtek: Add realtek,rtd-gpio bindings Krzysztof Kozlowski
2023-11-02 3:11 ` TY_Chang[張子逸]
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=20231101025802.3744-3-tychang@realtek.com \
--to=tychang@realtek.com \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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