From: Ulrich Hecht <uli+renesas@fpond.eu>
To: linux-renesas-soc@vger.kernel.org
Cc: netdev@vger.kernel.org, davem@davemloft.net,
linux-can@vger.kernel.org,
prabhakar.mahadev-lad.rj@bp.renesas.com,
biju.das.jz@bp.renesas.com, wsa@kernel.org,
yoshihiro.shimoda.uh@renesas.com, wg@grandegger.com,
mkl@pengutronix.de, kuba@kernel.org, mailhol.vincent@wanadoo.fr,
socketcan@hartkopp.net, geert@linux-m68k.org,
kieran.bingham@ideasonboard.com, horms@verge.net.au,
Ulrich Hecht <uli+renesas@fpond.eu>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v4 3/4] arm64: dts: renesas: r8a779a0-falcon: enable CANFD 0 and 1
Date: Wed, 9 Mar 2022 17:26:08 +0100 [thread overview]
Message-ID: <20220309162609.3726306-4-uli+renesas@fpond.eu> (raw)
In-Reply-To: <20220309162609.3726306-1-uli+renesas@fpond.eu>
Enables confirmed-working CAN interfaces 0 and 1 on the Falcon board.
Signed-off-by: Ulrich Hecht <uli+renesas@fpond.eu>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
.../boot/dts/renesas/r8a779a0-falcon.dts | 24 +++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts b/arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts
index e46dc9aa0a43..75e27f950ac0 100644
--- a/arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts
+++ b/arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts
@@ -65,4 +65,28 @@ pins_mii {
};
};
+
+ canfd0_pins: canfd0 {
+ groups = "canfd0_data";
+ function = "canfd0";
+ };
+
+ canfd1_pins: canfd1 {
+ groups = "canfd1_data";
+ function = "canfd1";
+ };
+};
+
+&canfd {
+ pinctrl-0 = <&canfd0_pins>, <&canfd1_pins>;
+ pinctrl-names = "default";
+ status = "okay";
+
+ channel0 {
+ status = "okay";
+ };
+
+ channel1 {
+ status = "okay";
+ };
};
--
2.30.2
next prev parent reply other threads:[~2022-03-09 16:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 16:26 [PATCH v4 0/4] can: rcar_canfd: Add support for V3U flavor Ulrich Hecht
2022-03-09 16:26 ` [PATCH v4 1/4] can: rcar_canfd: Add support for r8a779a0 SoC Ulrich Hecht
2022-03-10 1:14 ` Vincent MAILHOL
2022-03-09 16:26 ` [PATCH v4 2/4] arm64: dts: renesas: r8a779a0: Add CANFD device node Ulrich Hecht
2022-03-11 17:04 ` Geert Uytterhoeven
2022-03-09 16:26 ` Ulrich Hecht [this message]
2022-03-11 17:04 ` [PATCH v4 3/4] arm64: dts: renesas: r8a779a0-falcon: enable CANFD 0 and 1 Geert Uytterhoeven
2022-03-14 8:04 ` Geert Uytterhoeven
2022-03-09 16:26 ` [PATCH v4 4/4] dt-bindings: can: renesas,rcar-canfd: Document r8a779a0 support Ulrich Hecht
2022-03-10 8:25 ` [PATCH v4 0/4] can: rcar_canfd: Add support for V3U flavor Marc Kleine-Budde
2022-03-10 8:32 ` Ulrich Hecht
2022-03-10 8:45 ` Geert Uytterhoeven
2022-03-10 8:50 ` Marc Kleine-Budde
2022-03-11 4:20 ` patchwork-bot+netdevbpf
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=20220309162609.3726306-4-uli+renesas@fpond.eu \
--to=uli+renesas@fpond.eu \
--cc=biju.das.jz@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=kieran.bingham@ideasonboard.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=socketcan@hartkopp.net \
--cc=wg@grandegger.com \
--cc=wsa@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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;
as well as URLs for NNTP newsgroup(s).