From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>
Subject: [RFC PATCH 0/6] arm64: dts: renesas: add SWDT
Date: Sat, 20 Sep 2025 08:44:27 +0200 [thread overview]
Message-ID: <20250920064428.5544-8-wsa+renesas@sang-engineering.com> (raw)
I forgot over the years why we did not enable the SWDT on R-Car Gen3+.
The reason is that it is used by the firmware on Renesas boards.
However, this was not documented. So, based on a previous discussion
with Geert, here is an RFC how this documentation could look like:
* add the complete node to the SoC DTSI (here only R-Car H3, M3*)
* mark the node as "reserved" for the relevant boards
(firmware should have done that(tm))
If this approach is acceptable, I'd handle the other SoCs, too, of
course. Looking forward to comments! Passes dtbs_check here BTW.
Wolfram Sang (6):
arm64: dts: renesas: r8a77951: add SWDT node
arm64: dts: renesas: r8a77960: add SWDT node
arm64: dts: renesas: r8a77961: add SWDT node
arm64: dts: renesas: r8a77965: add SWDT node
arm64: dts: renesas: salvator-common: mark SWDT as reserved
arm64: dts: renesas: ulcb: mark SWDT as reserved
arch/arm64/boot/dts/renesas/r8a77951.dtsi | 10 ++++++++++
arch/arm64/boot/dts/renesas/r8a77960.dtsi | 10 ++++++++++
arch/arm64/boot/dts/renesas/r8a77961.dtsi | 10 ++++++++++
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 10 ++++++++++
arch/arm64/boot/dts/renesas/salvator-common.dtsi | 5 +++++
arch/arm64/boot/dts/renesas/ulcb.dtsi | 5 +++++
6 files changed, 50 insertions(+)
--
2.47.2
next reply other threads:[~2025-09-20 6:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 6:44 Wolfram Sang [this message]
2025-09-20 6:44 ` [RFC PATCH 1/6] arm64: dts: renesas: r8a77951: add SWDT node Wolfram Sang
2025-09-20 6:44 ` [RFC PATCH 2/6] arm64: dts: renesas: r8a77960: " Wolfram Sang
2025-09-20 6:44 ` [RFC PATCH 3/6] arm64: dts: renesas: r8a77961: " Wolfram Sang
2025-09-20 6:44 ` [RFC PATCH 4/6] arm64: dts: renesas: r8a77965: " Wolfram Sang
2025-09-20 6:44 ` [RFC PATCH 5/6] arm64: dts: renesas: salvator-common: mark SWDT as reserved Wolfram Sang
2025-09-20 6:44 ` [RFC PATCH 6/6] arm64: dts: renesas: ulcb: " Wolfram Sang
2025-09-22 12:46 ` [RFC PATCH 0/6] arm64: dts: renesas: add SWDT 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=20250920064428.5544-8-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--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).