From: Andrew Davis <afd@ti.com>
To: Neha Malcom Francis <n-francis@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Cc: <u-boot@lists.denx.de>, Andrew Davis <afd@ti.com>
Subject: [PATCH 6/6] arm: mach-k3: Move DRAM address of ATF for AM62/AM62a
Date: Wed, 14 Feb 2024 10:30:09 -0600 [thread overview]
Message-ID: <20240214163009.983034-7-afd@ti.com> (raw)
In-Reply-To: <20240214163009.983034-1-afd@ti.com>
The current address of TF-A in DRAM is just below the 512MB address line.
This means if the DRAM in a system is 512MB then TF-A is right at the
end of memory which is often reused, for instance U-Boot relocates itself
here. If a system has less than 512MB then that system wouldn't work at
all as TF-A would fail to load.
To avoid the issues above, move TF-A to the start of DRAM, which doesn't
change from system to system.
As TF-A is position independent, this has no dependency on TF-A. We
also fixup DT as needed when TF-A address is moved, so this change also
has no dependency on Linux and is fully forward/backward compatible.
Signed-off-by: Andrew Davis <afd@ti.com>
---
arch/arm/mach-k3/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-k3/Kconfig b/arch/arm/mach-k3/Kconfig
index 55bb874d9aa..33f20f61f83 100644
--- a/arch/arm/mach-k3/Kconfig
+++ b/arch/arm/mach-k3/Kconfig
@@ -123,7 +123,7 @@ config SYS_K3_SPL_ATF
config K3_ATF_LOAD_ADDR
hex "Load address of ATF image"
- default 0x9e780000 if (SOC_K3_AM625 || SOC_K3_AM62A7)
+ default 0x80000000 if (SOC_K3_AM625 || SOC_K3_AM62A7)
default 0x70000000
help
The load address for the ATF image. This value is used to build the
--
2.39.2
next prev parent reply other threads:[~2024-02-14 16:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 16:30 [PATCH 0/6] Move DRAM address of ATF Andrew Davis
2024-02-14 16:30 ` [PATCH 1/6] arm: mach-k3: Add default ATF location for AM62/AM62a Andrew Davis
2024-02-16 4:55 ` Neha Malcom Francis
2024-03-06 13:27 ` Bryan Brattlof
2024-06-19 11:49 ` Dhruva Gole
2024-06-19 18:20 ` Nishanth Menon
2024-06-19 20:02 ` Andrew Davis
2024-06-20 5:30 ` Wadim Egorov
2024-06-21 13:49 ` Bryan Brattlof
2024-02-14 16:30 ` [PATCH 2/6] arm: mach-k3: Add config option for setting OP-TEE address Andrew Davis
2024-02-16 4:59 ` Neha Malcom Francis
2024-02-28 6:21 ` Manorit Chawdhry
2024-03-06 13:49 ` Andrew Davis
2024-03-06 13:28 ` Bryan Brattlof
2024-02-14 16:30 ` [PATCH 3/6] arm: mach-k3: am62: Enable OF_SYSTEM_SETUP for all boards Andrew Davis
2024-02-14 16:30 ` [PATCH 4/6] arm: mach-k3: am62: Fixup TF-A/OP-TEE reserved-memory node in FDT Andrew Davis
2024-02-16 5:26 ` Neha Malcom Francis
2024-02-28 6:24 ` Manorit Chawdhry
2024-03-06 13:52 ` Andrew Davis
2024-03-06 13:35 ` Bryan Brattlof
2024-03-06 14:03 ` Andrew Davis
2024-03-06 15:38 ` Bryan Brattlof
2024-02-14 16:30 ` [PATCH 5/6] arm: mach-k3: am62a: " Andrew Davis
2024-03-06 13:35 ` Bryan Brattlof
2024-02-14 16:30 ` Andrew Davis [this message]
2024-02-15 8:06 ` [PATCH 6/6] arm: mach-k3: Move DRAM address of ATF for AM62/AM62a Francesco Dolcini
2024-02-15 20:44 ` Andrew Davis
2024-03-06 13:37 ` Bryan Brattlof
2024-03-06 16:53 ` [PATCH 0/6] Move DRAM address of ATF Tom Rini
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=20240214163009.983034-7-afd@ti.com \
--to=afd@ti.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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