display-caf: Squashed commits to support devices with JB video blobs

This should correct the retire fence, dequeue buffer, and mdp errors seen on some devices

It's confirmed to fix boot issues on htc s4 devices and the vzw gs3

Patch set 2: cleaned up duplicate ifdefs in common.mk
Patch set 3: update commit msg

hwc: Get the retire fence from the MDP driver

Get the retire fence separately instead of duplicating the
release fence.

Bug: 9319776
Change-Id: Iacb773c2d94f635e27a7b355d399cb2e36dac2a5
Signed-off-by: Iliyan Malchev <malchev@google.com>

Conflicts:
	common.mk

display: Add flag to allow legacy allocations from MM heap

 * New devices with IOMMU use the MM heap exclusively for protected
   buffers. We need to support the old behavior for devices with legacy
   userspace.
 * Enable the old behavior with TARGET_DISPLAY_INSECURE_MM_HEAP.

Change-Id: I7882354fa8f159c707be11d7021c18561abfb522

Conflicts:
	common.mk

Change-Id: Iacb773c2d94f635e27a7b355d399cb2e36dac2a5
display-caf: fix compile for device which don't use RETIRE_FENCE

the last squashed commit for qcom (http://goo.gl/YU90Ow) broke
compilation for Samsung Galaxy S4 variants.

it set TARGET_DISPLAY_USE_RETIRE_FENCE to true per default.
this sets it to false by default.

thanks to kufikugel for pointing this out in IRC!

Change-Id: Ice5987b8326bed784032731582f66d99e92d5135
Revert "display-caf: fix compile for device which don't use RETIRE_FENCE"

The original way is correct. 
This commit really confused me as the maintainers of other devices claim that the flag is being set without them making it true which can't be right.

Yup turns out that the flag was hidden in the BoardConfig somewhere.

This reverts commit 5f6d33fc201d868780f82c277180af43fb0436b4.

Change-Id: Id64662996d13059628d2704a61be0bd72765abee
Merge branch 'android-4.4' of https://github.com/omnirom/android_hardware_qcom_display-caf into android-4.4