From b793e43166348772af74331df7be46d7a696a7aa Mon Sep 17 00:00:00 2001 From: Sandrine Bailleux Date: Fri, 9 May 2014 11:35:36 +0100 Subject: fvp: Provide per-EL MMU setup functions Instead of having a single version of the MMU setup functions for all bootloader images that can execute either in EL3 or in EL1, provide separate functions for EL1 and EL3. Each bootloader image can then call the appropriate version of these functions. The aim is to reduce the amount of code compiled in each BL image by embedding only what's needed (e.g. BL1 to embed only EL3 variants). Change-Id: Ib86831d5450cf778ae78c9c1f7553fe91274c2fa --- bl32/tsp/aarch64/tsp_entrypoint.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'bl32') diff --git a/bl32/tsp/aarch64/tsp_entrypoint.S b/bl32/tsp/aarch64/tsp_entrypoint.S index 97d54f65..aeb54bc4 100644 --- a/bl32/tsp/aarch64/tsp_entrypoint.S +++ b/bl32/tsp/aarch64/tsp_entrypoint.S @@ -203,7 +203,7 @@ func tsp_cpu_on_entry * Initialise the MMU * --------------------------------------------- */ - bl enable_mmu + bl enable_mmu_el1 /* --------------------------------------------- * Give ourselves a stack allocated in Normal -- cgit v1.2.3