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

Hi Simon, Am Dienstag, 22. Oktober 2019, 14:08:04 CEST schrieb Heiko Stübner: > Am Dienstag, 22. Oktober 2019, 02:17:00 CEST schrieb Simon Glass: > > On Mon, 7 Oct 2019 at 18:22, Heiko Stuebner wrote: > > > > > > The loading convention for optee or any other tee on arm64 is as bl32 > > > paramete

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

Hi Simon, Am Dienstag, 22. Oktober 2019, 02:17:00 CEST schrieb Simon Glass: > On Mon, 7 Oct 2019 at 18:22, Heiko Stuebner wrote: > > > > 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 m

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

Hi Heiko, [+Igor] On Tue, Oct 8, 2019 at 2:22 AM Heiko Stuebner wrote: > > 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 > int

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

Hi Heiko, On Mon, 7 Oct 2019 at 18:22, Heiko Stuebner wrote: > > 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

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

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 jumps to bl33. All of them