On Tue, Feb 04, 2025 at 06:55:19PM -0700, Simon Glass wrote: > Where the bloblist is located in internal memory and TF-A's BL31 blob > removes access to this memory, the best option seems to be to relocate > the bloblist just before running TF-A. > > Add an option to select this behaviour and provide a relocation address. > > Signed-off-by: Simon Glass <s...@chromium.org> > --- > > common/Kconfig | 20 ++++++++++++++++++++ > common/bloblist.c | 15 ++++++++++++++- > common/spl/spl.c | 9 +++++++++ > 3 files changed, 43 insertions(+), 1 deletion(-) > > diff --git a/common/Kconfig b/common/Kconfig > index 0e8c44f3f74..962e7fd76eb 100644 > --- a/common/Kconfig > +++ b/common/Kconfig > @@ -1125,6 +1125,26 @@ config SPL_BLOBLIST_ALLOC > > endchoice > > +config SPL_BLOBLIST_RELOC > + bool "Relocate the bloblist before existing SPL" > + depends on BLOBLIST_FIXED > + help > + Some platforms locate the bloblist in SRAM in SPL. In some cases, > + the TF-A BL31 blob removes access to SRAM, e.g. with Rockchip RK3399. > + > + Enable this option to make U-Boot copy the bloblist from SRAM to SDRAM > + before leaving SPL.
Isn't this because TF-A is (re?-)initializing SDRAM? I'll let one of the Rockchip people chime in here, thanks. -- Tom
signature.asc
Description: PGP signature
