From: Ben Zong-You Xie <ben717@andestech.com>
Cc: <andi.shyti@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <linux-i2c@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<pjw@kernel.org>, <palmer@dabbelt.com>, <aou@eecs.berkeley.edu>,
<alex@ghiti.fr>, <linux-riscv@lists.infradead.org>,
Ben Zong-You Xie <ben717@andestech.com>
Subject: [PATCH 1/4] dt-bindings: i2c: add support for Andes I2C controller
Date: Thu, 15 Jan 2026 22:52:41 +0800 [thread overview]
Message-ID: <20260115145244.435890-2-ben717@andestech.com> (raw)
In-Reply-To: <20260115145244.435890-1-ben717@andestech.com>
Document device tree bindings for Andes I2C controller.
Signed-off-by: Ben Zong-You Xie <ben717@andestech.com>
---
.../bindings/i2c/andestech,atciic100.yaml | 44 +++++++++++++++++++
1 file changed, 44 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/andestech,atciic100.yaml
diff --git a/Documentation/devicetree/bindings/i2c/andestech,atciic100.yaml b/Documentation/devicetree/bindings/i2c/andestech,atciic100.yaml
new file mode 100644
index 000000000000..dcbcafc8d6bd
--- /dev/null
+++ b/Documentation/devicetree/bindings/i2c/andestech,atciic100.yaml
@@ -0,0 +1,44 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/i2c/andestech,atciic100.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Andes I2C controller on QiLai SoC and AE350 platform
+
+maintainers:
+ - Ben Zong-You Xie <ben717@andestech.com>
+
+allOf:
+ - $ref: /schemas/i2c/i2c-controller.yaml#
+
+properties:
+ compatible:
+ items:
+ - enum:
+ - andestech,qilai-i2c
+ - andestech,ae350-i2c
+ - const: andestech,atciic100
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+ - interrupts
+
+unevaluatedProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ i2c@30800000 {
+ compatible = "andestech,qilai-i2c","andestech,atciic100";
+ reg = <0x30800000 0x100000>;
+ interrupts = <6 IRQ_TYPE_LEVEL_HIGH>;
+ };
--
2.34.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-01-15 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 14:52 [PATCH 0/4] Add I2C support for QiLai SoC Ben Zong-You Xie
2026-01-15 14:52 ` Ben Zong-You Xie [this message]
2026-01-16 8:56 ` [PATCH 1/4] dt-bindings: i2c: add support for Andes I2C controller Krzysztof Kozlowski
2026-01-15 14:52 ` [PATCH 2/4] drivers: i2c: add the driver " Ben Zong-You Xie
2026-01-16 8:57 ` Krzysztof Kozlowski
2026-01-22 7:32 ` Andi Shyti
2026-01-15 14:52 ` [PATCH 3/4] MAINTAINERS: add an entry for Andes I2C driver Ben Zong-You Xie
2026-01-15 14:52 ` [PATCH 4/4] riscv: dts: andes: qilai: add I2C controller Ben Zong-You Xie
2026-01-22 14:14 ` [PATCH 0/4] Add I2C support for QiLai SoC Ben Zong-You Xie
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=20260115145244.435890-2-ben717@andestech.com \
--to=ben717@andestech.com \
--cc=alex@ghiti.fr \
--cc=andi.shyti@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@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