exynos5420: Clear the framebuffer before making it uncacheable
If we clear the framebuffer and then flush it back to memory using cache operations, the writes are going to be full cachelines at a time. If we make it uncacheable first, the writes will be serialized writes of whatever sized chunks memset uses, probably 4 bytes or less. BUG=None TEST=None BRANCH=None Change-Id: I59d6699fcea1c5ca4402ae6cf45df9c14878943a Signed-off-by: Gabe Black <gabeblack@google.com> Signed-off-by: Stefan Reinauer <reinauer@google.com> Reviewed-on: https://gerrit.chromium.org/gerrit/55837 Reviewed-by: Gabe Black <gabeblack@chromium.org> Reviewed-by: David Hendricks <dhendrix@chromium.org> Commit-Queue: Stefan Reinauer <reinauer@chromium.org>
This commit is contained in:
parent
e2216b3c43
commit
d8b782c3c7
1 changed files with 2 additions and 1 deletions
|
|
@ -97,6 +97,8 @@ static void exynos_displayport_init(device_t dev)
|
|||
lcdbase = (uintptr_t)cbmem_add(CBMEM_ID_CONSOLE, fb_size);
|
||||
printk(BIOS_SPEW, "LCD framebuffer base is %p\n", (void *)(lcdbase));
|
||||
|
||||
memset((void *)lcdbase, 0, fb_size); /* clear the framebuffer */
|
||||
|
||||
/*
|
||||
* We need to clean and invalidate the framebuffer region and disable
|
||||
* caching as well. We assume that our dcache <--> memory address
|
||||
|
|
@ -114,7 +116,6 @@ static void exynos_displayport_init(device_t dev)
|
|||
mmio_resource(dev, 1, lcdbase/KiB, (fb_size + KiB - 1)/KiB);
|
||||
printk(BIOS_DEBUG,
|
||||
"Initializing Exynos VGA, base %p\n", (void *)lcdbase);
|
||||
memset((void *)lcdbase, 0, fb_size); /* clear the framebuffer */
|
||||
ret = lcd_ctrl_init(fb_size, &panel, (void *)lcdbase);
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue