From: Marek Vasut <marek.vasut@mailbox.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-renesas-soc@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: renesas: sparrow-hawk: don't reserve SWDT
Date: Mon, 27 Oct 2025 19:21:11 +0100 [thread overview]
Message-ID: <29497db1-9a85-4c27-a0cb-eeee839c3797@mailbox.org> (raw)
In-Reply-To: <CAMuHMdXs+FoL5g4ZgFVQ4WwXRt9Y-8BcX27d7=wFFROa939CwQ@mail.gmail.com>
On 10/27/25 11:09 AM, Geert Uytterhoeven wrote:
Hello Geert,
> My Gray Hawk Single still has downstream firmware, and I can modify the
> SWDT registers from U-Boot (unlike on Salvator-XS with R-Car H3 ES2),
> so access is not blocked.
> Hence I plan to drop the SWDT patches for all R-Car Gen4 boards.
Thank you for testing. You can also flip the DIP switches on WhiteHawk
to boot the original firmware on it, it is left unmodified . Then we
would know whether even the WH is unaffected, but I suspect it likely is.
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2025-10-27 18:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 11:51 [PATCH] arm64: dts: renesas: sparrow-hawk: don't reserve SWDT Wolfram Sang
2025-10-17 11:54 ` Marek Vasut
2025-10-20 13:07 ` Geert Uytterhoeven
2025-10-20 19:48 ` Wolfram Sang
2025-10-21 7:09 ` Geert Uytterhoeven
2025-10-21 13:14 ` Marek Vasut
2025-10-21 13:22 ` Geert Uytterhoeven
2025-10-21 16:07 ` Marek Vasut
2025-10-22 7:01 ` Wolfram Sang
2025-10-27 10:09 ` Geert Uytterhoeven
2025-10-27 18:21 ` Marek Vasut [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=29497db1-9a85-4c27-a0cb-eeee839c3797@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.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).