stm32mp: Enable OP-TEE and TZC support in SPL
Subsystems (3)
v4 cover stm32mp: Enable OP-TEE and TZC support in SPL
The purpose of this series is to allow booting an OP-TEE image from SPL, by corectly configuring the TrustZone (TZC) memory regions.
Although TZC400 is a generic silicon logic that could apply to other mach- families, support is currently restricted to stm32mp. I have neither a feasible way nor interest in validating this for other chips. It's fairly trivial to move the code from mach- to arch/, should another use case arise.
The configuration of the memory regions is devicetree-driven, so there isn't much to hardcode, However the delineation between OP-TEE secure memory and shared memory is not given in the devicetree. This is the one thing that has to be hardcoded.
Changes since v3:
- Pass a "phys_size_t *" to ofnode_get_addr_size() to resolve warning
- s/u-boot,dm-pre-reloc/u-boot,dm-spl/ in devicetree for clarity
Changes since v2:
- Use ram_get_info() instead of ofnode_read("st,mem-size")
- Only hardcode shared memory size instead of TZDRAM size
- Use log_info() instead of pr_info()
Changes since v1:
- Removed "Weak functions are stupid" comment
- Addressed blank line complaints from checkpatch
Alexandru Gagniuc (5):
spl: mmc: Support OP-TEE payloads in Falcon mode
spl: Introduce spl_board_prepare_for_optee() hook
arm: stm32mp: Implement support for TZC 400 controller
stm32mp1: spl: Configure TrustZone controller for OP-TEE
ARM: dts: stm32mp: Add OP-TEE reserved memory to SPL dtb
arch/arm/dts/stm32mp157a-dk1-u-boot.dtsi | 3 + arch/arm/mach-stm32mp/Makefile | 1 + arch/arm/mach-stm32mp/include/mach/tzc.h | 33 ++++++ arch/arm/mach-stm32mp/spl.c | 92 +++++++++++++++ arch/arm/mach-stm32mp/tzc400.c | 136 +++++++++++++++++++++++ common/spl/spl.c | 5 + common/spl/spl_mmc.c | 6 +- include/spl.h | 14 +++ 8 files changed, 288 insertions(+), 2 deletions(-) create mode 100644 arch/arm/mach-stm32mp/include/mach/tzc.h create mode 100644 arch/arm/mach-stm32mp/tzc400.c
Signature · 1 line
2.31.1
PATCH v4 1/5 spl: mmc: Support OP-TEE payloads in Falcon mode
In general, Falcon mode means we're booting a linux kernel directly. With FIT images, however, an OP-TEE secure kernel can be booted before linux. Thus, if the next stage is an IH_OS_TEE, this isn't necessarily a problem.
Of course, a general solution would involve mmc_load_image_raw_os() only loading the binary, and leaving the decision of suitability to someone else. However, a rework of the boot flow is beyond the scope of this patch. Accept IH_OS_TEE as a valid OS value.
--- common/spl/spl_mmc.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
common/spl/spl_mmc.c +4 -2
@@ -230,8 +230,10 @@ static int mmc_load_image_raw_os(struct spl_image_info *spl_image,if (ret)return ret; -if (spl_image->os !=IH_OS_LINUX ) { -puts ("Expected Linux image is not found. Trying to start U-boot\n" ); +if (spl_image->os !=IH_OS_LINUX && spl_image->os !=IH_OS_TEE ) { +puts ("Expected OS image is not found. Instead found " ); +puts (genimg_get_os_name (spl_image->os)); +puts (". Trying to start U-boot\n" );return -ENOENT ; }
Signature · 1 line
2.31.1
Re: [PATCH v4 1/5] spl: mmc: Support OP-TEE payloads in Falcon mode
Hi,
Quoted 24 lines · Alexandru Gagniuc
In general, Falcon mode means we're booting a linux kernel directly. With FIT images, however, an OP-TEE secure kernel can be booted before linux. Thus, if the next stage is an
IH_OS_TEE, this isn't necessarily a problem.Of course, a general solution would involve
mmc_load_image_raw_os()only loading the binary, and leaving the decision of suitability to someone else. However, a rework of the boot flow is beyond the scope of this patch. AcceptIH_OS_TEEas a valid OS value.Signed-off-by Alexandru Gagniuc <[email protected]>Reviewed-by Tom Rini <[email protected]>Reviewed-by Patrick Delaunay <[email protected]>--- common/spl/spl_mmc.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)common/spl/spl_mmc.c +0
-0@@ -230,8 +230,10 @@ static int mmc_load_image_raw_os(struct spl_image_info *spl_image,if (ret)return ret;
common/spl/spl_mmc.c static int mmc_load_image_raw_os(struct spl_image_info *spl_image, · line 239
Quoted 10 lines
common/spl/spl_mmc.c +4
-2-if (spl_image->os !=IH_OS_LINUX ) { -puts ("Expected Linux image is not found. Trying to start U-boot\n" ); +if (spl_image->os !=IH_OS_LINUX && spl_image->os !=IH_OS_TEE ) { +puts ("Expected OS image is not found. Instead found " ); +puts (genimg_get_os_name (spl_image->os)); +puts (". Trying to start U-boot\n" );return -ENOENT ; }
When I merge this patch on master branch, I get the error:
arm: + imx6dl_mamoj
+===================== WARNING ====================== +This board does not use CONFIG_DM_USB (Driver Model +for USB). Please update the board to use +CONFIG_DM_USB before the v2019.07 release. Failure to +update by the deadline may result in board removal. +See doc/driver-model/migration.rst for more info.
+====================================================
+spl/u-boot-spl.bin exceeds file size limit:
+ limit: 0xefa0 bytes
+ actual: 0xf41d bytes
+ excess: 0x47d bytes
+make[1]: *** [Makefile:1997: spl/u-boot-spl.bin] Error 1 +make[1]: *** Deleting file 'spl/u-boot-spl.bin' +make: *** [Makefile:177: sub-make] Error 2
The overhead:
$> tools/buildman/buildman -b TEST -c 2 imx6dl_mamoj
$> tools/buildman/buildman -b TEST -c 2 imx6dl_mamoj -seS
Summary of 2 commits for 1 boards (1 thread, 12 jobs per thread)
01: Merge branch '2021-07-14-build-and-host-updates'
arm: w+ imx6dl_mamoj
+===================== WARNING ======================
+This board does not use CONFIG_DM_USB (Driver Model
+for USB). Please update the board to use
+CONFIG_DM_USB before the v2019.07 release. Failure to
+update by the deadline may result in board removal.
+See doc/driver-model/migration.rst for more info.
+====================================================
02: spl: mmc: Support OP-TEE payloads in Falcon mode
arm: + imx6dl_mamoj
+spl/u-boot-spl.bin exceeds file size limit:
+ limit: 0xefa0 bytes
+ actual: 0xf41d bytes
+ excess: 0x47d bytes
+make[1]: *** [Makefile:1997: spl/u-boot-spl.bin] Error 1
+make[1]: *** Deleting file 'spl/u-boot-spl.bin'
+make: *** [Makefile:177: sub-make] Error 2
arm: (for 1/1 boards) spl/u-boot-spl:all +2242.0 spl/u-boot-spl:rodata +2162.0 spl/u-boot-spl:text +80.0
With details :
diff 01_gc11f5abce8_Merge-branch-\'2021-0/imx6dl_mamoj/spl-u-boot-spl.sizes 02_g0620649bfa_spl--mmc--Support-OP/imx6dl_mamoj/spl-u-boot-spl.sizes 157a158,159
Quoted 2 lines
00000012 T
get_table_entry
00000012 Tget_table_entry_name
171a174
Quoted 1 line
00000014 T
genimg_get_os_name
531a535
Quoted 1 line
000000a8ruimage_os
563d566
< 00000134 T spl_mmc_load
566a570
Quoted 1 line
0000014cTspl_mmc_load
This issue need to be solved before I accept and merge the serie.
See also ./common/spl/spl_fit.c:514:
............ This saves some
* space by omitting the large table of OS types.
*/
But I think again about the title of this patch :
- spl: mmc: Support OP-TEE payloads in Falcon mode
If I unterstood after the serie the sequence for MMC is:
ROM code => SPL => TEE (as raw OS) => U-Boot
but it is not really the Falcon mode and
OP-TEE + falcon mode is not really supported...
And the patch title is disturbing.
For me the correct sequence is in Falcon mode is :
ROM code => SPL => TEE (secure world) => kernel (normal world)
With the TEE and the kernel loaded by the SPL......
and without falcon mode :
(A) ROM code => SPL => TEE (secure world) => U-Boot
or
(B) ROM code => SPL (TZ) => U-Boot (TZ) execute bootm => TEE (secure world) => kernel
what it your expected sequence in spl_load_simple_fit in this serie / in your defconfig ?
Today with the normal world address can be:
1/ = spl_image->entry_point (bootm_os.c in U-Boot proprer)
2/ = CONFIG_SYS_TEXT_BASE (hardcoded for SPL in spl_optee.S)
for 2/ When U-Boot is not used after SPL = in falcon mode,
the LR register shoud be set to kernel entry point.
Patrick
Re: [PATCH v4 1/5] spl: mmc: Support OP-TEE payloads in Falcon mode
Quoted 1 line · Patrick DELAUNAY
Hi,
[snip]
Quoted 11 lines
When I merge this patch on master branch, I get the error:
arm: +
imx6dl_mamoj(quoted diff) +7
-0+spl/u-boot-spl.bin exceeds file size limit: + limit: 0xefa0 bytes + actual: 0xf41d bytes + excess: 0x47d bytes +make[1]: *** [Makefile:1997: spl/u-boot-spl.bin] Error 1 +make[1]: *** Deleting file 'spl/u-boot-spl.bin' +make: *** [Makefile:177: sub-make] Error 2
Quoted 1 line
This issue need to be solved before I accept and merge the serie.
Okay, I'll have to drop the call to genimg_get_os_name().
Quoted 14 lines
But I think again about the title of this patch :
- spl: mmc: Support OP-TEE payloads in Falcon mode
If I unterstood after the serie the sequence for MMC is:
ROM code => SPL => TEE (as raw OS) => U-Boot
but it is not really the Falcon mode and
OP-TEE + falcon mode is not really supported...
Quoted 7 lines
And the patch title is disturbing.
For me the correct sequence is in Falcon mode is :
ROM code => SPL => TEE (secure world) => kernel (normal world)
This is exactly the use case that this patch intends to support.
Quoted 17 lines
With the TEE and the kernel loaded by the SPL......
and without falcon mode :
(A) ROM code => SPL => TEE (secure world) => U-Boot
or
(B) ROM code => SPL (TZ) => U-Boot (TZ) execute bootm => TEE (secure world) => kernel
what it your expected sequence in
spl_load_simple_fitin this serie / in your defconfig ?Today with the normal world address can be:
Quoted 8 lines
1/ =
spl_image->entry_point(bootm_os.cin U-Boot proprer)2/ =
CONFIG_SYS_TEXT_BASE(hardcoded for SPL inspl_optee.S)for 2/ When U-Boot is not used after SPL = in falcon mode,
the LR register shoud be set to kernel entry point.
How does SPL know where OP-TEE should jump to? One could parse the FIT image, and try to figure out which of the loadables is the kernel. But what if there's a linux and u-boot, with different "/configurations" nodes? Figuring out where OP-TEE wants to start the normal world is a hard problem that the u=boot infrastructure is not prepared for.
The solution I'm using is to build OP-TEE with
CFG_NS_ENTRY_ADDR=[linux entry addr]
Then LR is irrelevant.
Alex
v5 cover stm32mp: Enable OP-TEE and TZC support in SPL
In reply to Patrick DELAUNAYv4 branch was reported to have some issues with SPL becoming too big on some platforms (e.g. imx6dl_mamoj) This is fixed by dropping the call to genimg_get_os_name().
Alexandru Gagniuc (5):
spl: mmc: Support OP-TEE payloads in Falcon mode
spl: Introduce spl_board_prepare_for_optee() hook
arm: stm32mp: Implement support for TZC 400 controller
stm32mp1: spl: Configure TrustZone controller for OP-TEE
ARM: dts: stm32mp: Add OP-TEE reserved memory to SPL dtb
arch/arm/dts/stm32mp157a-dk1-u-boot.dtsi | 3 + arch/arm/mach-stm32mp/Makefile | 1 + arch/arm/mach-stm32mp/include/mach/tzc.h | 33 ++++++ arch/arm/mach-stm32mp/spl.c | 92 +++++++++++++++ arch/arm/mach-stm32mp/tzc400.c | 136 +++++++++++++++++++++++ common/spl/spl.c | 5 + common/spl/spl_mmc.c | 4 +- include/spl.h | 14 +++ 8 files changed, 286 insertions(+), 2 deletions(-) create mode 100644 arch/arm/mach-stm32mp/include/mach/tzc.h create mode 100644 arch/arm/mach-stm32mp/tzc400.c
Signature · 1 line
2.31.1
PATCH v5 1/5 spl: mmc: Support OP-TEE payloads in Falcon mode
In general, Falcon mode means we're booting a linux kernel directly. With FIT images, however, an OP-TEE secure kernel can be booted before linux. Thus, if the next stage is an IH_OS_TEE, this isn't necessarily a problem.
Of course, a general solution would involve mmc_load_image_raw_os() only loading the binary, and leaving the decision of suitability to someone else. However, a rework of the boot flow is beyond the scope of this patch. Accept IH_OS_TEE as a valid OS value.
--- common/spl/spl_mmc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
common/spl/spl_mmc.c +2 -2
@@ -230,8 +230,8 @@ static int mmc_load_image_raw_os(struct spl_image_info *spl_image,if (ret)return ret; -if (spl_image->os !=IH_OS_LINUX ) { -puts ("Expected Linux image is not found. Trying to start U-boot\n" ); +if (spl_image->os !=IH_OS_LINUX && spl_image->os !=IH_OS_TEE ) { +puts ("Expected image is not found. Trying to start U-boot\n" );return -ENOENT ; }
Signature · 1 line
2.31.1
Re: [PATCH v5 1/5] spl: mmc: Support OP-TEE payloads in Falcon mode
Hi,
Quoted 10 lines · Alexandru Gagniuc
In general, Falcon mode means we're booting a linux kernel directly. With FIT images, however, an OP-TEE secure kernel can be booted before linux. Thus, if the next stage is an
IH_OS_TEE, this isn't necessarily a problem.Of course, a general solution would involve
mmc_load_image_raw_os()only loading the binary, and leaving the decision of suitability to someone else. However, a rework of the boot flow is beyond the scope of this patch. AcceptIH_OS_TEEas a valid OS value.
Quoted 7 lines
Signed-off-by Alexandru Gagniuc <[email protected]>Reviewed-by Tom Rini <[email protected]>Reviewed-by Patrick Delaunay <[email protected]>--- common/spl/spl_mmc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Applied to u-boot-stm/master, thanks!
Regards
Patrick
PATCH v5 2/5 spl: Introduce spl_board_prepare_for_optee() hook
In reply to Alexandru GagniucOP-TEE requires some particular setup, which is not needed for linux or other payloads. Add a hook for platform-specific code to perform any OP-TEE related configuration and initialization.
A weak function is used because it is symmetrical to other spl_board_prepare_for_*() implementations. A solution to avoid the use of weak functions would trivially apply to all these implementations. However, re-designing this is beyond the scope of this patch.
--- common/spl/spl.c | 5 +++++ include/spl.h | 14 ++++++++++++++ 2 files changed, 19 insertions(+)
common/spl/spl.c +5 -0
@@ -167,6 +167,10 @@ __weak void spl_board_prepare_for_linux(void)/* Nothing to do! */ } +__weak void spl_board_prepare_for_optee (void *fdt) +{ +} +__weak void spl_board_prepare_for_boot (void ) {/* Nothing to do! */
@@ -747,6 +751,7 @@ void board_init_r(gd_t *dummy1, ulong dummy2)#if CONFIG_IS_ENABLED (OPTEE )case IH_OS_TEE :debug ("Jumping to U-Boot via OP-TEE\n" ); +spl_board_prepare_for_optee (spl_image.fdt_addr);spl_optee_entry (NULL ,NULL , spl_image.fdt_addr, (void *)spl_image.entry_point);break ;
include/spl.h +14 -0
@@ -388,6 +388,20 @@ int spl_parse_image_header(struct spl_image_info *spl_image, const struct image_header *header);void spl_board_prepare_for_linux (void ); + +/** +* spl_board_prepare_for_optee() - Prepare board for an OPTEE payload +* +* Prepares the board for booting an OP-TEE payload. Initialization is platform +* specific, and may include configuring the TrustZone memory, and other +* initialization steps required by OP-TEE. +* Note that @fdt is not used directly by OP-TEE. OP-TEE passes this @fdt to +* its normal world target. This target is not guaranteed to be u-boot, so @fdt +* changes that would normally be done by u-boot should be done in this step. +* +* @fdt: Devicetree that will be passed on, or NULL +*/ +void spl_board_prepare_for_optee (void *fdt);void spl_board_prepare_for_boot (void );int spl_board_ubi_load_image (u32 boot_device);int spl_board_boot_device (u32 boot_device);
Signature · 1 line
2.31.1
Re: [PATCH v5 2/5] spl: Introduce spl_board_prepare_for_optee() hook
Hi,
Quoted 9 lines · Alexandru Gagniuc
OP-TEE requires some particular setup, which is not needed for linux or other payloads. Add a hook for platform-specific code to perform any OP-TEE related configuration and initialization.
A weak function is used because it is symmetrical to other spl_board_prepare_for_*() implementations. A solution to avoid the use of weak functions would trivially apply to all these implementations. However, re-designing this is beyond the scope of this patch.
Quoted 8 lines
Signed-off-by Alexandru Gagniuc <[email protected]>Reviewed-by Tom Rini <[email protected]>Reviewed-by Simon Glass <[email protected]>Reviewed-by Patrick Delaunay <[email protected]>--- common/spl/spl.c | 5 +++++ include/spl.h | 14 ++++++++++++++ 2 files changed, 19 insertions(+)
Applied to u-boot-stm/master, thanks!
Regards
Patrick
PATCH v5 3/5 arm: stm32mp: Implement support for TZC 400 controller
In reply to Alexandru GagniucThe purpose of this change is to allow configuring TrustZone (TZC) memory permissions. For example, OP-TEE expects TZC regions to be configured in a very particular way. The API presented here is intended to allow exactly that.
UCLASS support is not implemented, because it would not be too useful. Changing TZC permissions needs to be done with care, so as not to cut off access to memory we are currently using. One place where we can use this is at the end of SPL, right before jumping to OP-TEE.
--- arch/arm/mach-stm32mp/Makefile | 1 + arch/arm/mach-stm32mp/include/mach/tzc.h | 33 ++++++ arch/arm/mach-stm32mp/tzc400.c | 136 +++++++++++++++++++++++ 3 files changed, 170 insertions(+) create mode 100644 arch/arm/mach-stm32mp/include/mach/tzc.h create mode 100644 arch/arm/mach-stm32mp/tzc400.c
arch/arm/mach-stm32mp/Makefile +1 -0
@@ -10,6 +10,7 @@ obj-y += bsec.o ifdef CONFIG_SPL_BUILD obj-y += spl.o +obj-y += tzc400.o else obj-y += cmd_stm32prog/ obj-$(CONFIG_CMD_STM32KEY) += cmd_stm32key.o
arch/arm/mach-stm32mp/include/mach/tzc.h new file +33 -0
@@ -0,0 +1,33 @@ +/* SPDX-License-Identifier: GPL-2.0+ */ +/* +* Simple API for configuring TrustZone memory regions +* +* The premise is that the desired TZC layout is known beforehand, and it can +* be configured in one step. tzc_configure() provides this functionality. +*/ +#ifndef MACH_TZC_H +#define MACH_TZC_H + +#include <linux/types.h> + +enum tzc_sec_mode { +TZC_ATTR_SEC_NONE =0 , +TZC_ATTR_SEC_R =1 , +TZC_ATTR_SEC_W =2 , +TZC_ATTR_SEC_RW =3 +}; + +struct tzc_region { +uintptr_t base; +uintptr_t top; +enum tzc_sec_mode sec_mode; +uint16_t nsec_id; +uint16_t filters_mask; +}; + +int tzc_configure (uintptr_t tzc,const struct tzc_region *cfg); +int tzc_disable_filters (uintptr_t tzc,uint16_t filters_mask); +int tzc_enable_filters (uintptr_t tzc,uint16_t filters_mask); +void tzc_dump_config (uintptr_t tzc); + +#endif /* MACH_TZC_H */
arch/arm/mach-stm32mp/tzc400.c new file +136 -0
136 lines not on this page · raw message
Signature · 1 line
2.31.1
Re: [PATCH v5 3/5] arm: stm32mp: Implement support for TZC 400 controller
Hi,
Quoted 12 lines · Alexandru Gagniuc
The purpose of this change is to allow configuring TrustZone (TZC) memory permissions. For example, OP-TEE expects TZC regions to be configured in a very particular way. The API presented here is intended to allow exactly that.
UCLASS support is not implemented, because it would not be too useful. Changing TZC permissions needs to be done with care, so as not to cut off access to memory we are currently using. One place where we can use this is at the end of SPL, right before jumping to OP-TEE.
Signed-off-by Alexandru Gagniuc <[email protected]>Reviewed-by Patrick Delaunay <[email protected]>
Quoted 8 lines
--- arch/arm/mach-stm32mp/Makefile | 1 + arch/arm/mach-stm32mp/include/mach/tzc.h | 33 ++++++ arch/arm/mach-stm32mp/tzc400.c | 136 +++++++++++++++++++++++ 3 files changed, 170 insertions(+)create mode 100644
arch/arm/mach-stm32mp/include/mach/tzc.hcreate mode 100644arch/arm/mach-stm32mp/tzc400.c
Applied to u-boot-stm/master, thanks!
Regards
Patrick
PATCH v5 4/5 stm32mp1: spl: Configure TrustZone controller for OP-TEE
In reply to Alexandru GagniucOP-TEE is very particular about how the TZC should be configured. When booting an OP-TEE payload, an incorrect TZC configuration will result in a panic.
Most information can be derived from the SPL devicetree. The only information we don't have is the split between TZDRAM and shared memory. This has to be hardcoded. The rest of the configuration is fairly easy, and only requires 3 TZC regions. Configure them.
--- arch/arm/mach-stm32mp/spl.c | 92 +++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+)
arch/arm/mach-stm32mp/spl.c +92 -0
@@ -11,11 +11,13 @@#include <hang.h> #include <init.h> #include <log.h> +#include <ram.h> #include <spl.h> #include <asm/cache.h> #include <asm/global_data.h> #include <asm/io.h> #include <asm/arch/sys_proto.h> +#include <mach/tzc.h> #include <linux/libfdt.h> u32 spl_boot_device (void )
@@ -92,6 +94,96 @@ __weak int board_early_init_f(void)return 0 ; } +uint32_t stm32mp_get_dram_size (void ) +{ +struct ram_info ram; +struct udevice *dev; +int ret; + +if (uclass_get_device (UCLASS_RAM ,0 , &dev)) +return 0 ; + + ret =ram_get_info (dev, &ram); +if (ret) +return 0 ; + +return ram.size; +} + +static int optee_get_reserved_memory (uint32_t *start,uint32_t *size) +{ +phys_size_t fdt_mem_size; +fdt_addr_t fdt_start; +ofnode node; + + node =ofnode_path ("/reserved-memory/optee" ); +if (!ofnode_valid (node)) +return 0 ; + + fdt_start =ofnode_get_addr_size (node,"reg" , &fdt_mem_size); + *start = fdt_start; + *size = fdt_mem_size; +return (fdt_start <0 ) ? fdt_start :0 ; +} + +#define CFG_SHMEM_SIZE 0x200000 +#define STM32_TZC_NSID_ALL 0xffff +#define STM32_TZC_FILTER_ALL 3 + +void stm32_init_tzc_for_optee (void ) +{ +const uint32_t dram_size =stm32mp_get_dram_size (); +const uintptr_t dram_top =STM32_DDR_BASE + (dram_size -1 ); +uint32_t optee_base, optee_size, tee_shmem_base; +const uintptr_t tzc =STM32_TZC_BASE ; +int ret; + +if (dram_size ==0 ) +panic ("Cannot determine DRAM size from devicetree\n" ); + + ret =optee_get_reserved_memory (&optee_base, &optee_size); +if (ret <0 || optee_size <=CFG_SHMEM_SIZE ) +panic ("Invalid OPTEE reserved memory in devicetree\n" ); + + tee_shmem_base = optee_base + optee_size -CFG_SHMEM_SIZE ; + +const struct tzc_region optee_config[] = { + { + .base =STM32_DDR_BASE , + .top = optee_base -1 , + .sec_mode =TZC_ATTR_SEC_NONE , + .nsec_id =STM32_TZC_NSID_ALL , + .filters_mask =STM32_TZC_FILTER_ALL , + }, { + .base = optee_base, + .top = tee_shmem_base -1 , + .sec_mode =TZC_ATTR_SEC_RW , + .nsec_id =0 , + .filters_mask =STM32_TZC_FILTER_ALL , + }, { + .base = tee_shmem_base, + .top = dram_top, + .sec_mode =TZC_ATTR_SEC_NONE , + .nsec_id =STM32_TZC_NSID_ALL , + .filters_mask =STM32_TZC_FILTER_ALL , + }, { + .top =0 , + } + }; + +flush_dcache_all (); + +tzc_configure (tzc, optee_config); +tzc_dump_config (tzc); + +dcache_disable (); +} + +void spl_board_prepare_for_optee (void *fdt) +{ +stm32_init_tzc_for_optee (); +} +void board_init_f (ulong dummy) {struct udevice *dev;
Signature · 1 line
2.31.1
Re: [PATCH v5 4/5] stm32mp1: spl: Configure TrustZone controller for OP-TEE
hI,
Quoted 9 lines · Alexandru Gagniuc
OP-TEE is very particular about how the TZC should be configured. When booting an OP-TEE payload, an incorrect TZC configuration will result in a panic.
Most information can be derived from the SPL devicetree. The only information we don't have is the split between TZDRAM and shared memory. This has to be hardcoded. The rest of the configuration is fairly easy, and only requires 3 TZC regions. Configure them.
Quoted 5 lines
Signed-off-by Alexandru Gagniuc <[email protected]>--- arch/arm/mach-stm32mp/spl.c | 92 +++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+)
Applied to u-boot-stm/master, thanks!
Regards
Patrick
PATCH v5 5/5 ARM: dts: stm32mp: Add OP-TEE reserved memory to SPL dtb
In reply to Alexandru GagniucAdd the "/reserved-memory/optee" node to the SPL devicetree. The purpose is to allow configuring TZC regions when booting OP-TEE.
--- arch/arm/dts/stm32mp157a-dk1-u-boot.dtsi | 3 +++ 1 file changed, 3 insertions(+)
arch/arm/dts/stm32mp157a-dk1-u-boot.dtsi +3 -0
@@ -30,9 +30,12 @@ }; reserved-memory { + u-boot,dm-spl; + optee@de000000 { reg = <0xde000000 0x02000000>; no-map; + u-boot,dm-spl; }; };
Signature · 1 line
2.31.1
Re: [PATCH v5 5/5] ARM: dts: stm32mp: Add OP-TEE reserved memory to SPL dtb
Hi,
Quoted 8 lines · Alexandru Gagniuc
Add the "/reserved-memory/optee" node to the SPL devicetree. The purpose is to allow configuring TZC regions when booting OP-TEE.
Signed-off-by Alexandru Gagniuc <[email protected]>Reviewed-by Simon Glass <[email protected]>--- arch/arm/dts/stm32mp157a-dk1-u-boot.dtsi | 3 +++ 1 file changed, 3 insertions(+)
Applied to u-boot-stm/master, thanks!
Regards
Patrick
Quoted 3 lines · Alexandru Gagniuc
v4 branch was reported to have some issues with SPL becoming too big on some platforms (e.g.
imx6dl_mamoj) This is fixed by dropping the call togenimg_get_os_name().
Ping for merge window.
Quoted 19 lines
Alexandru Gagniuc (5):
spl: mmc: Support OP-TEE payloads in Falcon mode
spl: Introducespl_board_prepare_for_optee()hook
arm: stm32mp: Implement support for TZC 400 controller
stm32mp1: spl: Configure TrustZone controller for OP-TEE
ARM: dts: stm32mp: Add OP-TEE reserved memory to SPL dtbarch/arm/dts/stm32mp157a-dk1-u-boot.dtsi | 3 + arch/arm/mach-stm32mp/Makefile | 1 + arch/arm/mach-stm32mp/include/mach/tzc.h | 33 ++++++ arch/arm/mach-stm32mp/spl.c | 92 +++++++++++++++ arch/arm/mach-stm32mp/tzc400.c | 136 +++++++++++++++++++++++ common/spl/spl.c | 5 + common/spl/spl_mmc.c | 4 +- include/spl.h | 14 +++ 8 files changed, 286 insertions(+), 2 deletions(-)create mode 100644
arch/arm/mach-stm32mp/include/mach/tzc.hcreate mode 100644arch/arm/mach-stm32mp/tzc400.c
PATCH v4 2/5 spl: Introduce spl_board_prepare_for_optee() hook
In reply to Alexandru GagniucOP-TEE requires some particular setup, which is not needed for linux or other payloads. Add a hook for platform-specific code to perform any OP-TEE related configuration and initialization.
A weak function is used because it is symmetrical to other spl_board_prepare_for_*() implementations. A solution to avoid the use of weak functions would trivially apply to all these implementations. However, re-designing this is beyond the scope of this patch.
--- common/spl/spl.c | 5 +++++ include/spl.h | 14 ++++++++++++++ 2 files changed, 19 insertions(+)
common/spl/spl.c +5 -0
@@ -165,6 +165,10 @@ __weak void spl_board_prepare_for_linux(void)/* Nothing to do! */ } +__weak void spl_board_prepare_for_optee (void *fdt) +{ +} +__weak void spl_board_prepare_for_boot (void ) {/* Nothing to do! */
@@ -745,6 +749,7 @@ void board_init_r(gd_t *dummy1, ulong dummy2)#if CONFIG_IS_ENABLED (OPTEE )case IH_OS_TEE :debug ("Jumping to U-Boot via OP-TEE\n" ); +spl_board_prepare_for_optee (spl_image.fdt_addr);spl_optee_entry (NULL ,NULL , spl_image.fdt_addr, (void *)spl_image.entry_point);break ;
include/spl.h +14 -0
@@ -388,6 +388,20 @@ int spl_parse_image_header(struct spl_image_info *spl_image, const struct image_header *header);void spl_board_prepare_for_linux (void ); + +/** +* spl_board_prepare_for_optee() - Prepare board for an OPTEE payload +* +* Prepares the board for booting an OP-TEE payload. Initialization is platform +* specific, and may include configuring the TrustZone memory, and other +* initialization steps required by OP-TEE. +* Note that @fdt is not used directly by OP-TEE. OP-TEE passes this @fdt to +* its normal world target. This target is not guaranteed to be u-boot, so @fdt +* changes that would normally be done by u-boot should be done in this step. +* +* @fdt: Devicetree that will be passed on, or NULL +*/ +void spl_board_prepare_for_optee (void *fdt);void spl_board_prepare_for_boot (void );int spl_board_ubi_load_image (u32 boot_device);int spl_board_boot_device (u32 boot_device);
Signature · 1 line
2.31.1
PATCH v4 3/5 arm: stm32mp: Implement support for TZC 400 controller
In reply to Alexandru GagniucThe purpose of this change is to allow configuring TrustZone (TZC) memory permissions. For example, OP-TEE expects TZC regions to be configured in a very particular way. The API presented here is intended to allow exactly that.
UCLASS support is not implemented, because it would not be too useful. Changing TZC permissions needs to be done with care, so as not to cut off access to memory we are currently using. One place where we can use this is at the end of SPL, right before jumping to OP-TEE.
--- arch/arm/mach-stm32mp/Makefile | 1 + arch/arm/mach-stm32mp/include/mach/tzc.h | 33 ++++++ arch/arm/mach-stm32mp/tzc400.c | 136 +++++++++++++++++++++++ 3 files changed, 170 insertions(+) create mode 100644 arch/arm/mach-stm32mp/include/mach/tzc.h create mode 100644 arch/arm/mach-stm32mp/tzc400.c
arch/arm/mach-stm32mp/Makefile +1 -0
@@ -10,6 +10,7 @@ obj-y += bsec.o ifdef CONFIG_SPL_BUILD obj-y += spl.o +obj-y += tzc400.o else obj-y += cmd_stm32prog/ obj-$(CONFIG_CMD_STM32KEY) += cmd_stm32key.o
arch/arm/mach-stm32mp/include/mach/tzc.h new file +33 -0
@@ -0,0 +1,33 @@ +/* SPDX-License-Identifier: GPL-2.0+ */ +/* +* Simple API for configuring TrustZone memory regions +* +* The premise is that the desired TZC layout is known beforehand, and it can +* be configured in one step. tzc_configure() provides this functionality. +*/ +#ifndef MACH_TZC_H +#define MACH_TZC_H + +#include <linux/types.h> + +enum tzc_sec_mode { +TZC_ATTR_SEC_NONE =0 , +TZC_ATTR_SEC_R =1 , +TZC_ATTR_SEC_W =2 , +TZC_ATTR_SEC_RW =3 +}; + +struct tzc_region { +uintptr_t base; +uintptr_t top; +enum tzc_sec_mode sec_mode; +uint16_t nsec_id; +uint16_t filters_mask; +}; + +int tzc_configure (uintptr_t tzc,const struct tzc_region *cfg); +int tzc_disable_filters (uintptr_t tzc,uint16_t filters_mask); +int tzc_enable_filters (uintptr_t tzc,uint16_t filters_mask); +void tzc_dump_config (uintptr_t tzc); + +#endif /* MACH_TZC_H */
arch/arm/mach-stm32mp/tzc400.c new file +136 -0
136 lines not on this page · raw message
Signature · 1 line
2.31.1
PATCH v4 4/5 stm32mp1: spl: Configure TrustZone controller for OP-TEE
In reply to Alexandru GagniucOP-TEE is very particular about how the TZC should be configured. When booting an OP-TEE payload, an incorrect TZC configuration will result in a panic.
Most information can be derived from the SPL devicetree. The only information we don't have is the split between TZDRAM and shared memory. This has to be hardcoded. The rest of the configuration is fairly easy, and only requires 3 TZC regions. Configure them.
--- arch/arm/mach-stm32mp/spl.c | 92 +++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+)
arch/arm/mach-stm32mp/spl.c +92 -0
@@ -11,11 +11,13 @@#include <hang.h> #include <init.h> #include <log.h> +#include <ram.h> #include <spl.h> #include <asm/cache.h> #include <asm/global_data.h> #include <asm/io.h> #include <asm/arch/sys_proto.h> +#include <mach/tzc.h> #include <linux/libfdt.h> u32 spl_boot_device (void )
@@ -92,6 +94,96 @@ __weak int board_early_init_f(void)return 0 ; } +uint32_t stm32mp_get_dram_size (void ) +{ +struct ram_info ram; +struct udevice *dev; +int ret; + +if (uclass_get_device (UCLASS_RAM ,0 , &dev)) +return 0 ; + + ret =ram_get_info (dev, &ram); +if (ret) +return 0 ; + +return ram.size; +} + +static int optee_get_reserved_memory (uint32_t *start,uint32_t *size) +{ +phys_size_t fdt_mem_size; +fdt_addr_t fdt_start; +ofnode node; + + node =ofnode_path ("/reserved-memory/optee" ); +if (!ofnode_valid (node)) +return 0 ; + + fdt_start =ofnode_get_addr_size (node,"reg" , &fdt_mem_size); + *start = fdt_start; + *size = fdt_mem_size; +return (fdt_start <0 ) ? fdt_start :0 ; +} + +#define CFG_SHMEM_SIZE 0x200000 +#define STM32_TZC_NSID_ALL 0xffff +#define STM32_TZC_FILTER_ALL 3 + +void stm32_init_tzc_for_optee (void ) +{ +const uint32_t dram_size =stm32mp_get_dram_size (); +const uintptr_t dram_top =STM32_DDR_BASE + (dram_size -1 ); +uint32_t optee_base, optee_size, tee_shmem_base; +const uintptr_t tzc =STM32_TZC_BASE ; +int ret; + +if (dram_size ==0 ) +panic ("Cannot determine DRAM size from devicetree\n" ); + + ret =optee_get_reserved_memory (&optee_base, &optee_size); +if (ret <0 || optee_size <=CFG_SHMEM_SIZE ) +panic ("Invalid OPTEE reserved memory in devicetree\n" ); + + tee_shmem_base = optee_base + optee_size -CFG_SHMEM_SIZE ; + +const struct tzc_region optee_config[] = { + { + .base =STM32_DDR_BASE , + .top = optee_base -1 , + .sec_mode =TZC_ATTR_SEC_NONE , + .nsec_id =STM32_TZC_NSID_ALL , + .filters_mask =STM32_TZC_FILTER_ALL , + }, { + .base = optee_base, + .top = tee_shmem_base -1 , + .sec_mode =TZC_ATTR_SEC_RW , + .nsec_id =0 , + .filters_mask =STM32_TZC_FILTER_ALL , + }, { + .base = tee_shmem_base, + .top = dram_top, + .sec_mode =TZC_ATTR_SEC_NONE , + .nsec_id =STM32_TZC_NSID_ALL , + .filters_mask =STM32_TZC_FILTER_ALL , + }, { + .top =0 , + } + }; + +flush_dcache_all (); + +tzc_configure (tzc, optee_config); +tzc_dump_config (tzc); + +dcache_disable (); +} + +void spl_board_prepare_for_optee (void *fdt) +{ +stm32_init_tzc_for_optee (); +} +void board_init_f (ulong dummy) {struct udevice *dev;
Signature · 1 line
2.31.1
Re: [PATCH v4 4/5] stm32mp1: spl: Configure TrustZone controller for OP-TEE
Hi Alexandru
Sorry for the delay, i just noticed that this patch didn't get reviewed neither by Patrick nor by me. That's done ;-)
Quoted 120 lines · Alexandru Gagniuc
OP-TEE is very particular about how the TZC should be configured. When booting an OP-TEE payload, an incorrect TZC configuration will result in a panic.
Most information can be derived from the SPL devicetree. The only information we don't have is the split between TZDRAM and shared memory. This has to be hardcoded. The rest of the configuration is fairly easy, and only requires 3 TZC regions. Configure them.
Signed-off-by Alexandru Gagniuc <[email protected]>--- arch/arm/mach-stm32mp/spl.c | 92 +++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+)arch/arm/mach-stm32mp/spl.c +85
-0@@ -11,11 +11,13 @@#include <hang.h> #include <init.h> #include <log.h> +#include <ram.h> #include <spl.h> #include <asm/cache.h> #include <asm/global_data.h> #include <asm/io.h> #include <asm/arch/sys_proto.h> +#include <mach/tzc.h> #include <linux/libfdt.h> u32 spl_boot_device (void )@@ -92,6 +94,96 @@ __weak int board_early_init_f(void)return 0 ; } +uint32_t stm32mp_get_dram_size (void ) +{ +struct ram_info ram; +struct udevice *dev; +int ret; + +if (uclass_get_device (UCLASS_RAM ,0 , &dev)) +return 0 ; + + ret =ram_get_info (dev, &ram); +if (ret) +return 0 ; + +return ram.size; +} + +static int optee_get_reserved_memory (uint32_t *start,uint32_t *size) +{ +phys_size_t fdt_mem_size; +fdt_addr_t fdt_start; +ofnode node; + + node =ofnode_path ("/reserved-memory/optee" ); +if (!ofnode_valid (node)) +return 0 ; + + fdt_start =ofnode_get_addr_size (node,"reg" , &fdt_mem_size); + *start = fdt_start; + *size = fdt_mem_size; +return (fdt_start <0 ) ? fdt_start :0 ; +} + +#define CFG_SHMEM_SIZE 0x200000 +#define STM32_TZC_NSID_ALL 0xffff +#define STM32_TZC_FILTER_ALL 3 + +void stm32_init_tzc_for_optee (void ) +{ +const uint32_t dram_size =stm32mp_get_dram_size (); +const uintptr_t dram_top =STM32_DDR_BASE + (dram_size -1 ); +uint32_t optee_base, optee_size, tee_shmem_base; +const uintptr_t tzc =STM32_TZC_BASE ; +int ret; + +if (dram_size ==0 ) +panic ("Cannot determine DRAM size from devicetree\n" ); + + ret =optee_get_reserved_memory (&optee_base, &optee_size); +if (ret <0 || optee_size <=CFG_SHMEM_SIZE ) +panic ("Invalid OPTEE reserved memory in devicetree\n" ); + + tee_shmem_base = optee_base + optee_size -CFG_SHMEM_SIZE ; + +const struct tzc_region optee_config[] = { + { + .base =STM32_DDR_BASE , + .top = optee_base -1 , + .sec_mode =TZC_ATTR_SEC_NONE , + .nsec_id =STM32_TZC_NSID_ALL , + .filters_mask =STM32_TZC_FILTER_ALL , + }, { + .base = optee_base, + .top = tee_shmem_base -1 , + .sec_mode =TZC_ATTR_SEC_RW , + .nsec_id =0 , + .filters_mask =STM32_TZC_FILTER_ALL , + }, { + .base = tee_shmem_base, + .top = dram_top, + .sec_mode =TZC_ATTR_SEC_NONE , + .nsec_id =STM32_TZC_NSID_ALL , + .filters_mask =STM32_TZC_FILTER_ALL , + }, { + .top =0 , + } + }; + +flush_dcache_all (); + +tzc_configure (tzc, optee_config); +tzc_dump_config (tzc); + +dcache_disable ();
arch/arm/mach-stm32mp/spl.c __weak int board_early_init_f(void) · line 189
Quoted 10 lines
arch/arm/mach-stm32mp/spl.c +7
-0+} + +void spl_board_prepare_for_optee (void *fdt) +{ +stm32_init_tzc_for_optee (); +} +void board_init_f (ulong dummy) {struct udevice *dev;
Thanks
Patrice
Re: [PATCH v4 4/5] stm32mp1: spl: Configure TrustZone controller for OP-TEE
In reply to Alexandru GagniucHi,
Quoted 9 lines · Alexandru Gagniuc
OP-TEE is very particular about how the TZC should be configured. When booting an OP-TEE payload, an incorrect TZC configuration will result in a panic.
Most information can be derived from the SPL devicetree. The only information we don't have is the split between TZDRAM and shared memory. This has to be hardcoded. The rest of the configuration is fairly easy, and only requires 3 TZC regions. Configure them.
Quoted 5 lines
Signed-off-by Alexandru Gagniuc <[email protected]>--- arch/arm/mach-stm32mp/spl.c | 92 +++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+)
Thanks
Patrick
PATCH v4 5/5 ARM: dts: stm32mp: Add OP-TEE reserved memory to SPL dtb
In reply to Alexandru GagniucAdd the "/reserved-memory/optee" node to the SPL devicetree. The purpose is to allow configuring TZC regions when booting OP-TEE.
--- arch/arm/dts/stm32mp157a-dk1-u-boot.dtsi | 3 +++ 1 file changed, 3 insertions(+)
arch/arm/dts/stm32mp157a-dk1-u-boot.dtsi +3 -0
@@ -30,9 +30,12 @@ }; reserved-memory { + u-boot,dm-spl; + optee@de000000 { reg = <0xde000000 0x02000000>; no-map; + u-boot,dm-spl; }; };
Signature · 1 line
2.31.1
Re: [PATCH v4 5/5] ARM: dts: stm32mp: Add OP-TEE reserved memory to SPL dtb
Hi,
Quoted 16 lines · Alexandru Gagniuc
Add the "/reserved-memory/optee" node to the SPL devicetree. The purpose is to allow configuring TZC regions when booting OP-TEE.
Signed-off-by Alexandru Gagniuc <[email protected]>Reviewed-by Simon Glass <[email protected]>--- arch/arm/dts/stm32mp157a-dk1-u-boot.dtsi | 3 +++ 1 file changed, 3 insertions(+)arch/arm/dts/stm32mp157a-dk1-u-boot.dtsi +0
-0@@ -30,9 +30,12 @@ };
arch/arm/dts/stm32mp157a-dk1-u-boot.dtsi line 41
Quoted 10 lines
arch/arm/dts/stm32mp157a-dk1-u-boot.dtsi +3
-0reserved-memory { + u-boot,dm-spl; + optee@de000000 { reg = <0xde000000 0x02000000>; no-map; + u-boot,dm-spl; }; };
Thanks
Patrick
Quoted 2 lines · Alexandru Gagniuc
The purpose of this series is to allow booting an OP-TEE image from SPL, by corectly configuring the TrustZone (TZC) memory regions.
Any chance we could have this hit the merge window?
Alex
Quoted 5 lines · Alex G.
Quoted 2 lines · Alexandru Gagniuc
The purpose of this series is to allow booting an OP-TEE image from SPL, by corectly configuring the TrustZone (TZC) memory regions.
Any chance we could have this hit the merge window?
For clarity, does this series depend on anything that's not already merged?
Signature · 1 line
Tom
Quoted 10 lines · Tom Rini
Quoted 5 lines · Alex G.
Quoted 2 lines · Alexandru Gagniuc
The purpose of this series is to allow booting an OP-TEE image from SPL, by corectly configuring the TrustZone (TZC) memory regions.
Any chance we could have this hit the merge window?
For clarity, does this series depend on anything that's not already merged?
Negative. This series can be applied standalone.
Alex