From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
<linux-renesas-soc@vger.kernel.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Steffen Pengel <spengel@de.adit-jv.com>,
Eugeniu Rosca <roscaeugeniu@gmail.com>,
Eugeniu Rosca <erosca@de.adit-jv.com>
Subject: [PATCH 1/2] arm64: dts: renesas: r8a77961: Add CAN{0,1} placeholder nodes
Date: Thu, 29 Oct 2020 14:37:40 +0100 [thread overview]
Message-ID: <20201029133741.25721-1-erosca@de.adit-jv.com> (raw)
With the same background and purpose as described in v4.20-rc1
commit 92bc66bfce99cd ("arm64: dts: renesas: r8a77965: Add CAN{0,1}
placeholder nodes"), add can0 and can1 placeholder nodes.
Signed-off-by: Eugeniu Rosca <erosca@de.adit-jv.com>
---
arch/arm64/boot/dts/renesas/r8a77961.dtsi | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r8a77961.dtsi b/arch/arm64/boot/dts/renesas/r8a77961.dtsi
index 1ba30313c8b8..d2a5ea20378f 100644
--- a/arch/arm64/boot/dts/renesas/r8a77961.dtsi
+++ b/arch/arm64/boot/dts/renesas/r8a77961.dtsi
@@ -1017,6 +1017,16 @@ avb: ethernet@e6800000 {
status = "disabled";
};
+ can0: can@e6c30000 {
+ reg = <0 0xe6c30000 0 0x1000>;
+ /* placeholder */
+ };
+
+ can1: can@e6c38000 {
+ reg = <0 0xe6c38000 0 0x1000>;
+ /* placeholder */
+ };
+
pwm0: pwm@e6e30000 {
compatible = "renesas,pwm-r8a77961", "renesas,pwm-rcar";
reg = <0 0xe6e30000 0 8>;
--
2.29.0
next reply other threads:[~2020-10-29 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 13:37 Eugeniu Rosca [this message]
2020-10-29 13:37 ` [PATCH 2/2] arm64: dts: renesas: r8a77961: ulcb-kf: Initial device tree Eugeniu Rosca
2020-10-29 14:09 ` Geert Uytterhoeven
2020-10-29 16:32 ` Eugeniu Rosca
2020-10-29 18:23 ` Geert Uytterhoeven
2020-10-30 9:07 ` Eugeniu Rosca
2020-10-30 9:14 ` Geert Uytterhoeven
2020-10-29 14:09 ` [PATCH 1/2] arm64: dts: renesas: r8a77961: Add CAN{0,1} placeholder nodes Geert Uytterhoeven
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=20201029133741.25721-1-erosca@de.adit-jv.com \
--to=erosca@de.adit-jv.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@kernel.org \
--cc=roscaeugeniu@gmail.com \
--cc=spengel@de.adit-jv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.