From: Marek Vasut <marek.vasut@mailbox.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org,
Conor Dooley <conor+dt@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>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: renesas: sparrow-hawk: Reserve first 128 MiB of DRAM
Date: Wed, 25 Mar 2026 14:52:45 +0100 [thread overview]
Message-ID: <78a1dcbf-64b6-4f3e-8d62-2bb9d26e9e20@mailbox.org> (raw)
In-Reply-To: <CAMuHMdVv5KUma8=2T+ibnXyH+45xvqVrQaPho0CSzP1_r+j_hQ@mail.gmail.com>
On 3/25/26 2:08 PM, Geert Uytterhoeven wrote:
Hello Geert,
>> --- a/arch/arm64/boot/dts/renesas/r8a779g3-sparrow-hawk.dts
>> +++ b/arch/arm64/boot/dts/renesas/r8a779g3-sparrow-hawk.dts
>> @@ -118,6 +118,17 @@ memory@600000000 {
>> reg = <0x6 0x00000000 0x1 0x00000000>;
>> };
>>
>> + reserved-memory {
>> + #address-cells = <2>;
>> + #size-cells = <2>;
>> + ranges;
>> +
>> + tfa@40000000 {
>> + reg = <0x0 0x40000000 0x0 0x8000000>;
>> + no-map;
>> + };
>> + };
>
> Obviously I don't like this very much, but I agree there is not much
> else we can do at this point. Shall I add a
>
> /* Temporary workaround for broken TFA BL31 */
>
> comment while applying?
For maximum backward compatibility even with old TFA BL31 versions,
which the users may run for whatever reason, I believe this reserved
memory area is here to stay and won't be "Temporary".
But I will be looking into TFA to fill in this reserved-memory node
properly for this and future SoCs.
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> i.e. will queue in renesas-fixes for v7.0.
Thank you
prev parent reply other threads:[~2026-03-25 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 14:33 [PATCH] arm64: dts: renesas: sparrow-hawk: Reserve first 128 MiB of DRAM Marek Vasut
2026-03-25 13:08 ` Geert Uytterhoeven
2026-03-25 13:52 ` 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=78a1dcbf-64b6-4f3e-8d62-2bb9d26e9e20@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=robh@kernel.org \
--cc=stable@vger.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