[PATCH] arm: mach-k3: am62p: Fixup TF-A/OP-TEE reserved-memory node in FDT

[Tom Rini]

On Thu, May 23, 2024 at 12:22:56PM -0500, Bryan Brattlof wrote:
> On May 23, 2024 thus sayeth Bryan Brattlof:
> > On May 23, 2024 thus sayeth Andrew Davis:
> > > On 5/23/24 11:43 AM, Bryan Brattlof wrote:
> > > > The address we load TFA and OPTEE is configurable by the
> > > > CONFIG_K3_{ATF,OPTEE)_LOAD_ADDR, but the DT node reservations remain
> > > > static which can cause some confusion about where exactly these firmware
> > > > are exactly. Fix this by updating the reserved-memory{} nodes when the
> > > > loaded address does not match the address in DT.
> > > > 
> > > > Reported-by: Andrew Davis <afd at ti.com>
> > > > Signed-off-by: Bryan Brattlof <bb at ti.com>
> > > > ---
> > > > Hello everyone,
> > > > 
> > > > This is a little fixup to avoid any confusion once we're in the kernel.
> > > > Because TF-A can be configured in U-Boot to be anywhere we want, we need
> > > > up update the reserved-memory{} node with this change.
> > > > 
> > > > Thanks for reviewing
> > > > ~Bryan
> > > > ---
> > > >   arch/arm/mach-k3/Makefile       |  1 +
> > > >   arch/arm/mach-k3/am62p5_fdt.c   | 16 ++++++++++++++++
> > > 
> > > You'll want to rebase this on -next, these _fdt.c files all got moved
> > > into directories for each SoC.
> > > 
> > 
> > Ah! my bad, you're right this belongs in -next. v2 incoming momentarily
> > 
> 
> Wait no on second thought, this needs to be in v2024.07 also. I'll leave 
> this for Tom for -master and maybe send out another version for -next to 
> preempt the merge conflict for v2024.10?

If this needs to go in master then git should hopefully do the right
thing when I merge the next rc tag in.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20240523/24a55b61/attachment.sig>