Searched hist:c1ad41fbf7d62b639b4aae387532b3a9f74851ed (Results 1 – 2 of 2) sorted by relevance
| /rk3399_ARM-atf/plat/st/common/ |
| H A D | stm32mp_common.c | c1ad41fbf7d62b639b4aae387532b3a9f74851ed Fri Sep 04 13:55:53 UTC 2020 Yann Gautier <yann.gautier@st.com> refactor(plat/st): map DDR secure at boot
In BL2, the DDR can be mapped as secured in MMU, as no other SW
has access to it during its execution.
The TZC400 configuration is also updated to reflect this. When using
OP-TEE, the TZC400 is reconfigured at the end of BL2, to match OP-TEE
mapping. Else, SP_min will be in charge to reconfigure TZC400 to set
DDR non-secure.
Change-Id: Ic5ec614b218f733796feeab1cdc425d28cc7c103
Signed-off-by: Yann Gautier <yann.gautier@st.com>
|
| /rk3399_ARM-atf/plat/st/stm32mp1/ |
| H A D | bl2_plat_setup.c | c1ad41fbf7d62b639b4aae387532b3a9f74851ed Fri Sep 04 13:55:53 UTC 2020 Yann Gautier <yann.gautier@st.com> refactor(plat/st): map DDR secure at boot
In BL2, the DDR can be mapped as secured in MMU, as no other SW
has access to it during its execution.
The TZC400 configuration is also updated to reflect this. When using
OP-TEE, the TZC400 is reconfigured at the end of BL2, to match OP-TEE
mapping. Else, SP_min will be in charge to reconfigure TZC400 to set
DDR non-secure.
Change-Id: Ic5ec614b218f733796feeab1cdc425d28cc7c103
Signed-off-by: Yann Gautier <yann.gautier@st.com>
|