From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, linux-can@vger.kernel.org,
kernel@pengutronix.de,
Geert Uytterhoeven <geert+renesas@glider.be>,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: [PATCH net-next 7/9] dt-bindings: can: renesas,rcar-canfd: Make interrupt-names required
Date: Mon, 16 May 2022 22:26:23 +0200 [thread overview]
Message-ID: <20220516202625.1129281-8-mkl@pengutronix.de> (raw)
In-Reply-To: <20220516202625.1129281-1-mkl@pengutronix.de>
From: Geert Uytterhoeven <geert+renesas@glider.be>
The Renesas R-Car CAN FD Controller always uses two or more interrupts.
Make the interrupt-names properties a required property, to make it
easier to identify the individual interrupts.
Update the example accordingly.
Link: https://lore.kernel.org/all/a68e65955e0df4db60233d468f348203c2e7b940.1651512451.git.geert+renesas@glider.be
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
---
.../devicetree/bindings/net/can/renesas,rcar-canfd.yaml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml b/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml
index 9fc137fafed9..6f71fc96bc4e 100644
--- a/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml
+++ b/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml
@@ -88,6 +88,7 @@ required:
- compatible
- reg
- interrupts
+ - interrupt-names
- clocks
- clock-names
- power-domains
@@ -136,7 +137,6 @@ then:
- const: rstc_n
required:
- - interrupt-names
- reset-names
else:
properties:
@@ -167,6 +167,7 @@ examples:
reg = <0xe66c0000 0x8000>;
interrupts = <GIC_SPI 29 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 30 IRQ_TYPE_LEVEL_HIGH>;
+ interrupt-names = "ch_int", "g_int";
clocks = <&cpg CPG_MOD 914>,
<&cpg CPG_CORE R8A7795_CLK_CANFD>,
<&can_clk>;
--
2.35.1
next prev parent reply other threads:[~2022-05-16 20:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 20:26 [PATCH net-next 0/9] pull-request: can-next 2022-05-16 Marc Kleine-Budde
2022-05-16 20:26 ` [PATCH net-next 1/9] can: raw: raw_sendmsg(): remove not needed setting of skb->sk Marc Kleine-Budde
2022-05-17 0:10 ` patchwork-bot+netdevbpf
2022-05-16 20:26 ` [PATCH net-next 2/9] can: raw: add support for SO_TXTIME/SCM_TXTIME Marc Kleine-Budde
2022-05-16 20:26 ` [PATCH net-next 3/9] can: isotp: add support for transmission without flow control Marc Kleine-Budde
2022-05-16 20:26 ` [PATCH net-next 4/9] can: isotp: isotp_bind(): return -EINVAL on incorrect CAN ID formatting Marc Kleine-Budde
2022-05-16 20:26 ` [PATCH net-next 5/9] can: ctucanfd: Let users select instead of depend on CAN_CTUCANFD Marc Kleine-Budde
2022-05-16 20:26 ` [PATCH net-next 6/9] can: slcan: slc_xmit(): use can_dropped_invalid_skb() instead of manual check Marc Kleine-Budde
2022-05-16 20:26 ` Marc Kleine-Budde [this message]
2022-05-16 20:26 ` [PATCH net-next 8/9] dt-bindings: can: ctucanfd: include common CAN controller bindings Marc Kleine-Budde
2022-05-16 20:26 ` [PATCH net-next 9/9] docs: ctucanfd: Use 'kernel-figure' directive instead of 'figure' Marc Kleine-Budde
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=20220516202625.1129281-8-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=geert+renesas@glider.be \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.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).