From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Duc Nguyen <duc.nguyen.ub@renesas.com>,
Wolfram Sang <wsa@kernel.org>
Subject: [RFC PATCH 3/3] arm64: dts: r8a779a0-falcon-cpu: Add TPU support
Date: Wed, 1 Sep 2021 11:17:25 +0200 [thread overview]
Message-ID: <20210901091725.35610-4-wsa+renesas@sang-engineering.com> (raw)
In-Reply-To: <20210901091725.35610-1-wsa+renesas@sang-engineering.com>
From: Duc Nguyen <duc.nguyen.ub@renesas.com>
This patch enables TPU channel 1 for the Falcon board.
Signed-off-by: Duc Nguyen <duc.nguyen.ub@renesas.com>
Signed-off-by: Wolfram Sang <wsa@kernel.org>
---
Do we want this activated upstream? I think it is nice to have.
arch/arm64/boot/dts/renesas/r8a779a0-falcon-cpu.dtsi | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a779a0-falcon-cpu.dtsi b/arch/arm64/boot/dts/renesas/r8a779a0-falcon-cpu.dtsi
index a0a1a1da0d87..cf777c2799e8 100644
--- a/arch/arm64/boot/dts/renesas/r8a779a0-falcon-cpu.dtsi
+++ b/arch/arm64/boot/dts/renesas/r8a779a0-falcon-cpu.dtsi
@@ -175,6 +175,11 @@ scif_clk_pins: scif_clk {
groups = "scif_clk";
function = "scif_clk";
};
+
+ tpu_pin: tpu {
+ groups = "tpu_to1";
+ function = "tpu";
+ };
};
&rwdt {
@@ -193,3 +198,10 @@ &scif0 {
&scif_clk {
clock-frequency = <24000000>;
};
+
+&tpu {
+ pinctrl-0 = <&tpu_pin>;
+ pinctrl-names = "default";
+
+ status = "okay";
+};
--
2.30.2
next prev parent reply other threads:[~2021-09-01 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 9:17 [PATCH 0/3] v3u: add support for TPU Wolfram Sang
2021-09-01 9:17 ` [PATCH 1/3] clk: renesas: r8a779a0: Add TPU clock Wolfram Sang
2021-09-06 9:36 ` Geert Uytterhoeven
2021-09-01 9:17 ` [PATCH 2/3] arm64: dts: renesas: r8a779a0: Add TPU node Wolfram Sang
2021-09-06 9:38 ` Geert Uytterhoeven
2021-09-01 9:17 ` Wolfram Sang [this message]
2021-09-06 9:45 ` [RFC PATCH 3/3] arm64: dts: r8a779a0-falcon-cpu: Add TPU support Geert Uytterhoeven
2021-09-06 9:50 ` Wolfram Sang
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=20210901091725.35610-4-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=duc.nguyen.ub@renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa@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).