Re: [U-Boot] [PATCH v2 3/4] image: fdt: copy possible optee nodes to a loaded devicetree

Hi Heiko, > > Hi Patrick, > > Am Mittwoch, 23. Oktober 2019, 09:10:52 CEST schrieb Patrick DELAUNAY: > > Hi Jens and Heiko, > > > > > From: U-Boot On Behalf Of Jens > > > Wiklander > > > Sent: mercredi 23 octobre 2019 08:46 > > > > > > On Tue, Oct 22, 2019 at 09:04:27PM +0200, Heiko Stuebner

Re: [U-Boot] [PATCH v2 3/4] image: fdt: copy possible optee nodes to a loaded devicetree

Hi Patrick, Am Mittwoch, 23. Oktober 2019, 09:10:52 CEST schrieb Patrick DELAUNAY: > Hi Jens and Heiko, > > > From: U-Boot On Behalf Of Jens Wiklander > > Sent: mercredi 23 octobre 2019 08:46 > > > > On Tue, Oct 22, 2019 at 09:04:27PM +0200, Heiko Stuebner wrote: > > > From: Heiko Stuebner >

Re: [U-Boot] [PATCH v2 3/4] image: fdt: copy possible optee nodes to a loaded devicetree

Hi Jens and Heiko, > From: U-Boot On Behalf Of Jens Wiklander > Sent: mercredi 23 octobre 2019 08:46 > > On Tue, Oct 22, 2019 at 09:04:27PM +0200, Heiko Stuebner wrote: > > From: Heiko Stuebner > > > > The loading convention for optee or any other tee on arm64 is as bl32 > > parameter to the

Re: [U-Boot] [PATCH v2 3/4] image: fdt: copy possible optee nodes to a loaded devicetree

On Tue, Oct 22, 2019 at 09:04:27PM +0200, Heiko Stuebner wrote: > From: Heiko Stuebner > > The loading convention for optee or any other tee on arm64 is as bl32 > parameter to the trusted-firmware. So TF-A gets invoked with the TEE as > bl32 and main u-boot as bl33. Once it has done its startup

[U-Boot] [PATCH v2 3/4] image: fdt: copy possible optee nodes to a loaded devicetree

From: Heiko Stuebner The loading convention for optee or any other tee on arm64 is as bl32 parameter to the trusted-firmware. So TF-A gets invoked with the TEE as bl32 and main u-boot as bl33. Once it has done its startup TF-A jumps into the bl32 for the TEE startup, returns to TF-A and then