Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-arm-kernel@lists.infradead.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: r8a78000: Describe all reserved memory
Date: Mon, 18 May 2026 14:39:12 +0200	[thread overview]
Message-ID: <0404752d-ad50-4d10-bce3-85fcc249b754@mailbox.org> (raw)
In-Reply-To: <CAMuHMdVcpR96smOd4sdEXHoRp=WTLLzWNN9hO0P0=ZBTe4fKog@mail.gmail.com>

On 5/18/26 9:18 AM, Geert Uytterhoeven wrote:

Hello Geert,

>> +               /* TEE TZ DRAM. */
>> +               tee@8c400000 {
>> +                       reg = <0x0 0x8c400000 0x0 0x02000000>;
>> +                       no-map;
>> +               };
>> +        };
> 
> Shouldn't these reservations be added by the bootloader stack, when
> passing the DTB to Linux?

They should be added by the bootloader stack components, TFA and TEE, 
but they do not generate those reservation nodes thus far. TFA I can fix 
up for 2.16 (2.15 is in code freeze now), optee-os will need upstreaming 
of all the outstanding patches first, and then this can be fixed too. 
This is all long term plan though. Short term plan, which also prevents 
issues with SDK TFA/TEE, is this reserved memory node.

-- 
Best regards,
Marek Vasut


  reply	other threads:[~2026-05-18 12:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-17 16:31 [PATCH] arm64: dts: renesas: r8a78000: Describe all reserved memory Marek Vasut
2026-05-18  7:18 ` Geert Uytterhoeven
2026-05-18 12:39   ` Marek Vasut [this message]
2026-05-29  8:51 ` 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=0404752d-ad50-4d10-bce3-85fcc249b754@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=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