Linux CAN drivers development
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
	Vincent Mailhol <mailhol@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-can@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] dt-bindings: can: add arasan canfd controller
Date: Mon,  3 Aug 2026 22:05:30 +0800	[thread overview]
Message-ID: <20260803140531.12692-2-jszhang@kernel.org> (raw)
In-Reply-To: <20260803140531.12692-1-jszhang@kernel.org>

Add documentation for the arasan canfd controller.

Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
---
 .../bindings/net/can/arasan,canfd.yaml        | 63 +++++++++++++++++++
 1 file changed, 63 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/net/can/arasan,canfd.yaml

diff --git a/Documentation/devicetree/bindings/net/can/arasan,canfd.yaml b/Documentation/devicetree/bindings/net/can/arasan,canfd.yaml
new file mode 100644
index 000000000000..a120c11ce304
--- /dev/null
+++ b/Documentation/devicetree/bindings/net/can/arasan,canfd.yaml
@@ -0,0 +1,63 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/net/can/arasan,canfd.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title:
+  Arasan CAN-FD controller
+
+maintainers:
+  - Jisheng Zhang <jszhang@kernel.org>
+
+allOf:
+  - $ref: can-controller.yaml#
+
+properties:
+  compatible:
+    const: arasan,canfd
+
+  reg:
+    maxItems: 1
+
+  interrupts:
+    maxItems: 1
+
+  clocks:
+    maxItems: 2
+
+  clock-names:
+    items:
+      - const: can
+      - const: sys
+
+  resets:
+    maxItems: 2
+
+  reset-names:
+    items:
+      - const: can
+      - const: sys
+
+required:
+  - compatible
+  - reg
+  - interrupts
+  - clocks
+  - resets
+
+additionalProperties: false
+
+examples:
+  - |
+    #include <dt-bindings/interrupt-controller/arm-gic.h>
+    #include <dt-bindings/interrupt-controller/irq.h>
+    can@e5060000 {
+        compatible = "arasan,canfd";
+        reg = <0xe5060000 0x1000>;
+        interrupts = <GIC_SPI 163 IRQ_TYPE_LEVEL_HIGH>;
+        clocks = <&clk 32>, <&clk 16>;
+        clock-names = "can", "sys";
+        resets = <&rst 3>, <&rst 2>;
+        reset-names = "can", "sys";
+    };
-- 
2.53.0


  reply	other threads:[~2026-08-03 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 14:05 [PATCH 0/2] can: add arasan canfd controller support Jisheng Zhang
2026-08-03 14:05 ` Jisheng Zhang [this message]
2026-08-03 14:31   ` [PATCH 1/2] dt-bindings: can: add arasan canfd controller sashiko-bot
2026-08-03 15:17   ` Krzysztof Kozlowski
2026-08-03 14:05 ` [PATCH 2/2] can: arasan-canfd: add driver for arasan CAN-FD controller Jisheng Zhang
2026-08-03 14:43   ` sashiko-bot
2026-08-03 15:21   ` Philipp Zabel
2026-08-03 16:05   ` Oliver Hartkopp

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=20260803140531.12692-2-jszhang@kernel.org \
    --to=jszhang@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailhol@kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=p.zabel@pengutronix.de \
    --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