From b90f207a1d386ec391bd3ea9eb403c4ad7b7551b Mon Sep 17 00:00:00 2001 From: Hadi Asyrafi Date: Tue, 20 Aug 2019 15:33:27 +0800 Subject: Invalidate dcache build option for bl2 entry at EL3 Some of the platform (ie. Agilex) make use of CCU IPs which will only be initialized during bl2_el3_early_platform_setup. Any operation to the cache beforehand will crash the platform. Hence, this will provide an option to skip the data cache invalidation upon bl2 entry at EL3 Signed-off-by: Hadi Asyrafi Change-Id: I2c924ed0589a72d0034714c31be8fe57237d1f06 --- docs/getting_started/user-guide.rst | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/getting_started') diff --git a/docs/getting_started/user-guide.rst b/docs/getting_started/user-guide.rst index 48cbdb9f..3828d0b4 100644 --- a/docs/getting_started/user-guide.rst +++ b/docs/getting_started/user-guide.rst @@ -287,6 +287,12 @@ Common build options enable this use-case. For now, this option is only supported when BL2_AT_EL3 is set to '1'. +- ``BL2_INV_DCACHE``: This is an optional build option which control dcache + invalidation upon BL2 entry. Some platform cannot handle cache operations + during entry as the coherency unit is not yet initialized. This may cause + crashing. Leaving this option to '1' (default) will allow the operation. + This option is only relevant when BL2_AT_EL3 is set to '1'. + - ``BL31``: This is an optional build option which specifies the path to BL31 image for the ``fip`` target. In this case, the BL31 in TF-A will not be built. -- cgit v1.2.3