devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org,
	Conor Dooley <conor+dt@kernel.org>,
	 devicetree@vger.kernel.org,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh@kernel.org>
Subject: Re: [RFC PATCH 0/6] arm64: dts: renesas: add SWDT
Date: Mon, 22 Sep 2025 14:46:05 +0200	[thread overview]
Message-ID: <CAMuHMdVONJVkvBj_AYZxkCZ1Fhr95HGSMNbQa-nn6+NmZc-R-g@mail.gmail.com> (raw)
In-Reply-To: <20250920064428.5544-8-wsa+renesas@sang-engineering.com>

Hi Wolfram,

On Sat, 20 Sept 2025 at 08:44, Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> 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

Thanks for your series!

Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      parent reply	other threads:[~2025-09-22 12:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-20  6:44 [RFC PATCH 0/6] arm64: dts: renesas: add SWDT Wolfram Sang
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 ` Geert Uytterhoeven [this message]

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=CAMuHMdVONJVkvBj_AYZxkCZ1Fhr95HGSMNbQa-nn6+NmZc-R-g@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=robh@kernel.org \
    --cc=wsa+renesas@sang-engineering.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).