From: Elaine Zhang <zhangqing@rock-chips.com>
To: zhangqing@rock-chips.com, mkl@pengutronix.de,
kernel@pengutronix.de, mailhol.vincent@wanadoo.fr,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
heiko@sntech.de, cl@rock-chips.com
Cc: linux-can@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [RESEND PATCH v8 1/4] dt-bindings: can: rockchip_canfd: add rk3576 CAN controller
Date: Tue, 11 Nov 2025 16:05:11 +0800 [thread overview]
Message-ID: <20251111080511.2923069-1-zhangqing@rock-chips.com> (raw)
Add documentation for the rockchip rk3576 CAN controller.
Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
---
.../net/can/rockchip,rk3568v2-canfd.yaml | 52 +++++++++++++++++--
1 file changed, 48 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/net/can/rockchip,rk3568v2-canfd.yaml b/Documentation/devicetree/bindings/net/can/rockchip,rk3568v2-canfd.yaml
index a077c0330013..30782218728e 100644
--- a/Documentation/devicetree/bindings/net/can/rockchip,rk3568v2-canfd.yaml
+++ b/Documentation/devicetree/bindings/net/can/rockchip,rk3568v2-canfd.yaml
@@ -10,13 +10,12 @@ title:
maintainers:
- Marc Kleine-Budde <mkl@pengutronix.de>
-allOf:
- - $ref: can-controller.yaml#
-
properties:
compatible:
oneOf:
- - const: rockchip,rk3568v2-canfd
+ - enum:
+ - rockchip,rk3568v2-canfd
+ - rockchip,rk3576-can
- items:
- const: rockchip,rk3568v3-canfd
- const: rockchip,rk3568v2-canfd
@@ -43,6 +42,33 @@ properties:
- const: core
- const: apb
+ dmas:
+ maxItems: 1
+
+ dma-names:
+ items:
+ - const: rx
+
+allOf:
+ - $ref: can-controller.yaml#
+ - if:
+ properties:
+ compatible:
+ contains:
+ const: rockchip,rk3576-can
+ then:
+ properties:
+ dmas:
+ minItems: 1
+ maxItems: 1
+ dma-names:
+ minItems: 1
+ maxItems: 1
+ else:
+ properties:
+ dmas: false
+ dma-names: false
+
required:
- compatible
- reg
@@ -72,3 +98,21 @@ examples:
reset-names = "core", "apb";
};
};
+
+ - |
+ soc {
+ #address-cells = <2>;
+ #size-cells = <2>;
+
+ can@2ac00000 {
+ compatible = "rockchip,rk3576-can";
+ reg = <0x0 0x2ac00000 0x0 0x1000>;
+ interrupts = <GIC_SPI 121 IRQ_TYPE_LEVEL_HIGH>;
+ clocks = <&cru CLK_CAN0>, <&cru PCLK_CAN0>;
+ clock-names = "baud", "pclk";
+ resets = <&cru SRST_CAN0>, <&cru SRST_P_CAN0>;
+ reset-names = "core", "apb";
+ dmas = <&dmac0 20>;
+ dma-names = "rx";
+ };
+ };
--
2.34.1
next reply other threads:[~2025-11-11 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 8:05 Elaine Zhang [this message]
2025-11-11 9:26 ` [RESEND PATCH v8 1/4] dt-bindings: can: rockchip_canfd: add rk3576 CAN controller Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2025-11-12 1:59 [RESEND PATCH v8 0/4] rockchip: add can for RK3576 Soc Elaine Zhang
2025-11-12 1:59 ` [RESEND PATCH v8 1/4] dt-bindings: can: rockchip_canfd: add rk3576 CAN controller Elaine Zhang
2025-11-12 8:53 ` Marc Kleine-Budde
2025-11-12 10:06 ` zhangqing
2025-11-12 19:04 ` Conor Dooley
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=20251111080511.2923069-1-zhangqing@rock-chips.com \
--to=zhangqing@rock-chips.com \
--cc=cl@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@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;
as well as URLs for NNTP newsgroup(s).