aboutsummaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorLuden <luden@ghostmail.com>2016-02-15 19:53:10 +0100
committerZiyan <jaraidaniel@gmail.com>2016-03-11 01:07:57 +0100
commitc759a52251a0cb25b1d2460b53b22ae81dd172d4 (patch)
tree3cb77f5ebd6eae49c64d3548981ce783590eb0fe /arch
parent156204495a2e62a85d90a897242fd900b317be1a (diff)
downloadkernel_samsung_tuna-c759a52251a0cb25b1d2460b53b22ae81dd172d4.zip
kernel_samsung_tuna-c759a52251a0cb25b1d2460b53b22ae81dd172d4.tar.gz
kernel_samsung_tuna-c759a52251a0cb25b1d2460b53b22ae81dd172d4.tar.bz2
Removed garbage on the screen during early boot.
Change-Id: I76aabb05867233b6e7b84b512bae5f5a640ab589
Diffstat (limited to 'arch')
-rw-r--r--arch/arm/plat-omap/android-display.c33
1 files changed, 33 insertions, 0 deletions
diff --git a/arch/arm/plat-omap/android-display.c b/arch/arm/plat-omap/android-display.c
index c044b59..ad0acb7 100644
--- a/arch/arm/plat-omap/android-display.c
+++ b/arch/arm/plat-omap/android-display.c
@@ -28,6 +28,31 @@
#include <plat/dsscomp.h>
#include <plat/vram.h>
+/* Default IOBUFS size guaranteed that the memory used for early boot
+ * framebuffer will be overlapped by IOBUFS allocation, therefore
+ * won't be written to and there will be no extra output until video
+ * driver is initialized properly.
+ *
+ * With smaller IOBUFS size that framebuffer area becomes exposed
+ * to the system, hence the phone displays all the random garbabe
+ * that's in that memory region until video driver is initialized.
+ *
+ * While harmless, it looks ugly, so we'd better correct it. The
+ * easiest way to do it is to force VRAM allocation during the boot
+ * that overlaps with earlier framebuffer address.
+ *
+ * Given that for tuna devices lcd_bootfb equals 0xbea70000 at
+ * the boot and VRAM size is 7.5MB, allocating VRAM at 0xbea00000
+ * ensures that LCD range is fully covered.
+ *
+ * Cleaner solution would be to parse that parameter and calculate
+ * the necessary address dynamically, but for now hard-coded value
+ * will do. */
+#define OMAP_VRAM_START 0xbea00000
+/* Make sure we override VRAM region only if IOBUFS is small enough
+ * so that we don't overlap with it. */
+#define OMAP_MAX_IOBUFS_SIZE ((OMAP_VRAM_START - 0xba300000) / 1024 / 1024)
+
struct omap_android_display_data {
/* members with default values */
u32 width;
@@ -191,8 +216,16 @@ static void set_vram_sizes(struct sgx_omaplfb_config *sgx_config,
vram += fb->mem_desc.region[i].size;
}
+#if defined(CONFIG_ION_OMAP_IPU_MEM_IOBUFS_SIZE) && \
+ CONFIG_ION_OMAP_IPU_MEM_IOBUFS_SIZE <= OMAP_MAX_IOBUFS_SIZE
+ /* See comments above for OMAP_VRAM_START for justification. */
+ pr_info("android_display: setting vram to %u at address 0x%x\n",
+ vram, OMAP_VRAM_START);
+ omap_vram_set_sdram_vram(vram, OMAP_VRAM_START);
+#else
pr_info("android_display: setting vram to %u\n", vram);
omap_vram_set_sdram_vram(vram, 0);
+#endif
}
static void set_ion_carveouts(struct sgx_omaplfb_config *sgx_config,