[coreboot-gerrit] Patch set updated for coreboot: f931d14 exynos5420: Don't disable and re-enable the MMU when uncaching the framebuffer

[Gabe Black (gabeblack@chromium.org)]

Gabe Black (gabeblack at chromium.org) just uploaded a new patch set to gerrit, which you can find at http://review.coreboot.org/3667

-gerrit

commit f931d1492857e70040a36fe6603a5bca7354a80d
Author: Stefan Reinauer <reinauer at chromium.org>
Date:   Mon May 20 15:21:48 2013 -0700

    exynos5420: Don't disable and re-enable the MMU when uncaching the framebuffer
    
    At one time it seemed to be necessary to disable and then re-enable the
    MMU when setting the framebuffer to be uncache-able due to bugs in the
    MMU management code. Since those bugs have been fixed, this is no longer
    necessary.
    
    Change-Id: I7ce825cf5eaaa95119364d780cba0935752e4632
    Signed-off-by: Gabe Black <gabeblack at chromium.org>
    Signed-off-by: Stefan Reinauer <reinauer at chromium.org>
---
 src/cpu/samsung/exynos5420/cpu.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/src/cpu/samsung/exynos5420/cpu.c b/src/cpu/samsung/exynos5420/cpu.c
index e83c16a..1d51174 100644
--- a/src/cpu/samsung/exynos5420/cpu.c
+++ b/src/cpu/samsung/exynos5420/cpu.c
@@ -105,15 +105,11 @@ static void exynos_displayport_init(device_t dev)
 	 * Note: We may want to do something clever to ensure the framebuffer
 	 * region is aligned such that we don't change dcache policy for other
 	 * stuff inadvertantly.
-	 *
-	 * FIXME: Is disabling/re-enabling the MMU entirely necessary?
 	 */
 	uint32_t lower = ALIGN_DOWN(lcdbase, MiB);
 	uint32_t upper = ALIGN_UP(lcdbase + fb_size, MiB);
 	dcache_clean_invalidate_by_mva(lower, upper - lower);
-	dcache_mmu_disable();
 	mmu_config_range(lower/MiB, (upper - lower)/MiB, DCACHE_OFF);
-	dcache_mmu_enable();
 
 	mmio_resource(dev, 1, lcdbase/KiB, (fb_size + KiB - 1)/KiB);
 	printk(BIOS_DEBUG,