[U-Boot-Users] [PATCH] 85xx: Don't icbi when unlocking the cache

There is no reason to icbi when invalidating the temporary stack in the d-cache. Its impossible on e500 to have the i-cache contain any addresses in the temp stack and it can be problematic in generating transactions on the bus to non-valid addresses.
Signed-off-by: Kumar Gala galak@kernel.crashing.org ---
in git://git.kernel.org/pub/scm/boot/u-boot/galak/u-boot.git mpc85xx
cpu/mpc85xx/start.S | 7 ++----- 1 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/cpu/mpc85xx/start.S b/cpu/mpc85xx/start.S index eb24dbc..f4c17f8 100644 --- a/cpu/mpc85xx/start.S +++ b/cpu/mpc85xx/start.S @@ -992,7 +992,6 @@ trap_reloc:
blr
-#ifdef CFG_INIT_RAM_LOCK .globl unlock_ram_in_cache unlock_ram_in_cache: /* invalidate the INIT_RAM section */ @@ -1002,11 +1001,9 @@ unlock_ram_in_cache: andi. r4,r4,0x1ff slwi r4,r4,(10 - 1 - L1_CACHE_SHIFT) mtctr r4 -1: icbi r0,r3 - dcbi r0,r3 +1: dcbi r0,r3 addi r3,r3,CFG_CACHELINE_SIZE bdnz 1b - sync /* Wait for all icbi to complete on bus */ + sync isync blr -#endif

On Tue, Feb 19, 2008 at 10:43 PM, Kumar Gala galak@kernel.crashing.org wrote:
There is no reason to icbi when invalidating the temporary stack in the d-cache. Its impossible on e500 to have the i-cache contain any addresses in the temp stack and it can be problematic in generating transactions on the bus to non-valid addresses.
Signed-off-by: Kumar Gala galak@kernel.crashing.org
Applied, with changes required due to applying to the same spot as the INIT_RAM fix.
Thanks, Andy
participants (2)
-
Andy Fleming
-
Kumar Gala