From: CL Wang <cl634@andestech.com>
To: 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>
Cc: CL Wang <cl634@andestech.com>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<tim609@andestech.com>
Subject: [PATCH 1/3] dt-bindings: gpio: Add support for ATCGPIO100 GPIO controller
Date: Mon, 16 Nov 2026 12:09:12 +0800 [thread overview]
Message-ID: <20261116040914.368298-2-cl634@andestech.com> (raw)
In-Reply-To: <20261116040914.368298-1-cl634@andestech.com>
Document devicetree bindings for the Andes ATCGPIO100 GPIO controller.
ATCGPIO100 is the name of the IP, which is integrated in the Andes AE350
platform and in SoCs such as Qilai. As in the ATCSPI200 SPI controller
binding, the compatibles follow the platform and SoC rather than the IP
name: andestech,ae350-gpio is the fallback, and an SoC that integrates
the IP adds its own compatible, such as andestech,qilai-gpio, in front
of it. Drivers can then match on the fallback and still add SoC-specific
handling later.
The controller has up to 32 lines, and ngpios gives the number of lines
implemented. The debounce logic can run from either of two clocks: pclk,
the APB bus clock, which is required, or extclk, an optional external
clock that allows longer debounce periods. The interrupt is optional, as
the controller also works as a plain GPIO controller without it.
Signed-off-by: CL Wang <cl634@andestech.com>
---
.../bindings/gpio/andestech,ae350-gpio.yaml | 92 +++++++++++++++++++
1 file changed, 92 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/andestech,ae350-gpio.yaml
diff --git a/Documentation/devicetree/bindings/gpio/andestech,ae350-gpio.yaml b/Documentation/devicetree/bindings/gpio/andestech,ae350-gpio.yaml
new file mode 100644
index 000000000000..01badd2a1342
--- /dev/null
+++ b/Documentation/devicetree/bindings/gpio/andestech,ae350-gpio.yaml
@@ -0,0 +1,92 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/gpio/andestech,ae350-gpio.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Andes ATCGPIO100 GPIO controller on AE350 platform
+
+maintainers:
+ - CL Wang <cl634@andestech.com>
+
+properties:
+ compatible:
+ oneOf:
+ - items:
+ - enum:
+ - andestech,qilai-gpio
+ - const: andestech,ae350-gpio
+ - const: andestech,ae350-gpio
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+ interrupt-controller: true
+
+ "#interrupt-cells":
+ const: 2
+
+ gpio-controller: true
+
+ "#gpio-cells":
+ const: 2
+
+ ngpios:
+ minimum: 1
+ maximum: 32
+
+ gpio-line-names:
+ minItems: 1
+ maxItems: 32
+
+ clocks:
+ minItems: 1
+ items:
+ - description: APB bus clock
+ - description: External clock for debounce
+
+ clock-names:
+ minItems: 1
+ items:
+ - const: pclk
+ - const: extclk
+
+patternProperties:
+ "^.+-hog(-[0-9]+)?$":
+ type: object
+ required:
+ - gpio-hog
+
+required:
+ - compatible
+ - reg
+ - gpio-controller
+ - "#gpio-cells"
+ - clocks
+ - clock-names
+
+additionalProperties: false
+
+dependencies:
+ interrupt-controller: [ interrupts, "#interrupt-cells" ]
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ gpio@f0700000 {
+ compatible = "andestech,ae350-gpio";
+ reg = <0xf0700000 0x100>;
+ interrupts = <7 IRQ_TYPE_LEVEL_HIGH>;
+ interrupt-parent = <&plic>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ gpio-controller;
+ #gpio-cells = <2>;
+ ngpios = <32>;
+ clocks = <&pclk>, <&extclk>;
+ clock-names = "pclk", "extclk";
+ };
--
2.34.1
next prev parent reply other threads:[~2026-11-16 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 4:09 [PATCH 0/3] gpio: Add support for Andes " CL Wang
2026-11-16 4:09 ` CL Wang [this message]
2026-11-16 4:09 ` [PATCH 2/3] gpio: atcgpio100: Add ATCGPIO100 GPIO driver CL Wang
2026-11-16 4:09 ` [PATCH 3/3] MAINTAINERS: Add entry for Andes ATCGPIO100 GPIO CL Wang
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=20261116040914.368298-2-cl634@andestech.com \
--to=cl634@andestech.com \
--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 \
--cc=tim609@andestech.com \
/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®