hwc: Blank and unblank primary on first boot

Change-Id: I246858f216d58e2e96a1faf1afac60372f3ddcab
Merge cm 'branch cm-11.0' into cm-11.0
Merge commit 'a8e98319cfa2db4db609a5997f6d1b0bd8a42671' into cm-11.0
Merge commit '214ad3311bf7cc1757072652b172c692959276b1' into cm-11.0
Merge commit '97abdefcfdd7a813178a3afcb8cf6433f9f120bb' into cm-11.0
hwc: Blank and unblank primary on first boot for msm7x30

I made this commit to workaround a strange issue we faced on our Samsung Galaxy S Plus (GT-I9001)
after switching to ION and updated Adreno drivers (Vanilla drivers released on April 2013 by Qualcomm).

After completing the boot and before the first screen off, sometimes the boot splash screen appeared
during app transitions, instead of completely blank screen, for example when starting video playback,
while the first load of the keyboard... The problem happened on CM 10.2 and CM 11.0, not on CM 10.1.

I haven't found another solution at the moment, but probably we're missing something on kernel side (framebuffer driver).

Change-Id: Ib57ae5bf43ac46f2b6d7bd6f3473be5ca529f7a8
overlay: Allocate from MM heap as a fallback

 * Not all devices support IOMMU yet, so use the MM heap as a fallback.

Change-Id: I9d9f3dffb92f5b4bf45422df0f66a40611943202
hwcomposer: Use RGB_BORDERFILL only on MDP 4.2 and higher.

MDP 4.0 does not support RGB_BORDERFILL and causes the display to fail
initializing.

Patch Set 2: Actually set MDP_RGB format if not BORDERFILL.

Change-Id: Ib2007221c4dc78fd17ced97c0a0d28896c877b80
gralloc : Don't fallback to system heap for framebuffer allocations

MDP can not handle buffers from system heap, so try camera heap
first, before falling back completely to system heap

Change-Id: I7e2ab0094be5d1075be1ca93295cf54b84101835
display: Cover NO_IOMMU for msm7x30 too

Change-Id: Ic68672f386a06fd0ac9fd1f18eec3188415a8642
Merge from ADC
Clean
gitignore
Merge branch 'cm-11.0' of https://github.com/DarkCyanogenMod/android_hardware_qcom_display-caf into cm-11.0