feat(bl2): support RESET_TO_BL2 and ENABLE_RMEWhen RSE is used as the root of trust along with CPU that supports RMEthere is a need to enable both RESET_TO_BL2 and ENABLE_RME.In current bl2_main
feat(bl2): support RESET_TO_BL2 and ENABLE_RMEWhen RSE is used as the root of trust along with CPU that supports RMEthere is a need to enable both RESET_TO_BL2 and ENABLE_RME.In current bl2_main there are two different code paths for RESET_BL2,one handles BL2 running in EL1 and other for BL2 running in EL3.When RME is enabled, BL2 always runs at EL3 but the current flow callsbl2_early_platform_setup2, bl2_plat_arch_setup instead ofbl2_el3_early_platform_setup, bl2_el3_plat_arch_setup. Adding RME,TRANSFER_LIST, ROMLIB support in bl2_el3_* helpers makesarm_bl2_el3_setup.c almost identical to arm_bl2_setup.c.This patch removes bl2_el3_plat helpers and related files. Now differentcombinations of RESET_TO_BL2, ENABLE_RME are handled in common bl2_setuproutines in arm_bl2_setup.c. This helps to have common place to supportnew features and build flags for BL2 irrespective of which EL the BL2runs.BREAKING-CHANGE: This patch also changes all existing platform files andfunctions that use format bl2_el3_* to bl2_plat helpers. If any platformor out-of-tree platforms that need to support running BL2 in EL1 or EL3must now handle it in bl2_early_platform_setup2 and bl2_plat_arch_setup.Signed-off-by: Arunachalam Ganapathy <arunachalam.ganapathy@arm.com>Change-Id: I8d332dbe2de1db3b69319496c8d04626cdcf4140
show more ...
chore: remove MULTI_CONSOLE_API referencesMULTI_CONSOLE_API have been removed long time ago by commit 5b6ebeec9c99("Remove MULTI_CONSOLE_API flag and references to it") that's why removereference
chore: remove MULTI_CONSOLE_API referencesMULTI_CONSOLE_API have been removed long time ago by commit 5b6ebeec9c99("Remove MULTI_CONSOLE_API flag and references to it") that's why removereferences in platform.mk files and also in one rst which is not validanymore.Change-Id: I45f8e7db0a14ce63de62509100d8159b7aca2657Signed-off-by: Michal Simek <michal.simek@amd.com>
refactor(build): distinguish BL2 as TF-A entry point and BL2 running at EL3BL2_AT_EL3 is an overloaded macro which has two uses: 1. When BL2 is entry point into TF-A(no BL1) 2. When BL2 is runnin
refactor(build): distinguish BL2 as TF-A entry point and BL2 running at EL3BL2_AT_EL3 is an overloaded macro which has two uses: 1. When BL2 is entry point into TF-A(no BL1) 2. When BL2 is running at EL3 exception levelThese two scenarios are not exactly same even though first implicitlymeans second to be true. To distinguish between these two use cases weintroduce new macros.BL2_AT_EL3 is renamed to RESET_TO_BL2 to better convey both 1. and 2.Additional macro BL2_RUNS_AT_EL3 is added to cover all scenarious whereBL2 runs at EL3 (including four world systems).BREAKING CHANGE: BL2_AT_EL3 renamed to RESET_TO_BL2 across therepository.Change-Id: I477e1d0f843b44b799c216670e028fcb3509fb72Signed-off-by: Arvind Ram Prakash <arvind.ramprakash@arm.com>Signed-off-by: Maksims Svecovs <maksims.svecovs@arm.com>
refactor(plat/imx/imx): make imx io-storage logic for TBBR/FIP commonThis commit makes imx image io-storage logic common for allimx platform.Signed-off-by: Ying-Chun Liu (PaulLiu) <paulliu@debia
refactor(plat/imx/imx): make imx io-storage logic for TBBR/FIP commonThis commit makes imx image io-storage logic common for allimx platform.Signed-off-by: Ying-Chun Liu (PaulLiu) <paulliu@debian.org>Change-Id: I15045ac8f9dfa8cb714e32f9e7475d5eae4e86e4
fix(plat/imx): do not keep mmc_device_info in stackCreate a dedicated static struct mmc_device_info mmc_info mmc_infoinstead of having this in stack.A boot issue has been seen on some platform wh
fix(plat/imx): do not keep mmc_device_info in stackCreate a dedicated static struct mmc_device_info mmc_info mmc_infoinstead of having this in stack.A boot issue has been seen on some platform when applying patch [1]. [1] 13f3c5166f1 ("mmc:prevent accessing to the released space in case of wrong usage")Signed-off-by: Yann Gautier <yann.gautier@foss.st.com>Change-Id: Iba0424a5787f9e510a60696d4033db1b49b243b2
imx: Unify Platform specific defines for PSCI modulePLATFORM_CORE_COUNT - Unsigned intPLATFORM_CLUSTER_COUNT - Unsigned intPLATFORM_MAX_CPUS_PER_CLUSTER - Unsigned intPLATFORM_CORE_COUNT_PER_CLU
imx: Unify Platform specific defines for PSCI modulePLATFORM_CORE_COUNT - Unsigned intPLATFORM_CLUSTER_COUNT - Unsigned intPLATFORM_MAX_CPUS_PER_CLUSTER - Unsigned intPLATFORM_CORE_COUNT_PER_CLUSTER - Unsigned intSigned-off-by: Deepika Bhavnani <deepika.bhavnani@arm.com>Change-Id: I8b19e833a4e1067e1cfcc9bfaede7854e0e63004
plat: imx7: Add PicoPi iMX7D basic supportThe PicoPi iMX7D is a 2 board development board consisting ofa System-on-Module and a carrier baseboard and optimized forthe Internet-of-Things (IoT).T
plat: imx7: Add PicoPi iMX7D basic supportThe PicoPi iMX7D is a 2 board development board consisting ofa System-on-Module and a carrier baseboard and optimized forthe Internet-of-Things (IoT).This patch add basic support to this board.Signed-off-by: Jun Nie <jun.nie@linaro.org>Reviewed-by: Louis Mayencourt <louis.mayencourt@arm.com>Change-Id: I009d85819c4f73b7063aab73d0f6ee74e6ef3fc4