Squashed commit of the following:

commit 00d3261233bfa488252f99d9eb4b0759a8e4748c
Merge: de825f2 2bfd180
Author: Ricardo Cerqueira <cyanogenmod@cerqueira.org>
Date:   Wed Jul 24 23:40:41 2013 +0100

    Merge tag 'android-4.3_r2.1' into cm-10.2

    Android 4.3 release 2.1

commit de825f2f08fad153116807ea18002e4590bd71bb
Author: Hashcode <hashcode0f@gmail.com>
Date:   Fri Dec 14 23:48:47 2012 -0800

    omap4xxx: add flag to allow custom libion

    Due to kernel changes I need to stop the omap4xxx/libion via
    BOARD_USES_CUSTOM_LIBION flag and instead use a custom libion
    in my device trees.

    Change-Id: Ic48e8c51456c76dfd9bca00cb59581deb2cfc510
    Signed-off-by: Hashcode <hashcode0f@gmail.com>

commit a1c078bd69103c62754f6ead655f1afec4b72179
Author: Hashcode <hashcode0f@gmail.com>
Date:   Sun Jan 20 21:18:50 2013 -0800

    [1/3] omap4xxx: Allow custom DOMX source instead of Google DOMX default

    Part 1 of 3 patches: To allow omap4 devices to use custom "domx" source
    via a new BoardConfig.mk item:
    TI_CUSTOM_DOMX_PATH := device/<manufacturer>/<device-name>/domx

    This setting provides for 3 changes during the build:
    1. In hardware/ti/omap4xxx this settings stops standard Google domx
    source from being built and changes the domx reference for tiutils.
    2. In frameworks/base it changes the default openmax references for
    frameworks/base/media/jni/mediaeditor/Android.mk to the new location
    3. In frameworks/av changes the openmax references in 5 places, and adds
    new includes in ACodec.cpp, CameraSource.cpp and OMXCodec.cpp

    This commit for hardware/ti/omap4xxx is based on this cherry-pick from
    omapzoom (with a more descriptive BoardConfig setting name):
    http://www.omapzoom.org/?p=platform/hardware/ti/omap4xxx.git;a=commitdiff;h=040534d546dbcfcff16ff1afff15c01c2822dfcc

    Change-Id: I32bf75073278639dc9e4442168c7b35295beb495
    Signed-off-by: Hashcode <hashcode0f@gmail.com>

commit 60c8c252813375efcb9276dbef25220d0ae2bee2
Author: Mykola Ostrovskyy <mykola@ti.com>
Date:   Tue Jul 10 15:24:29 2012 +0530

    hwc: Support HDMI as primary display

    This patch disables mirroring/docking logic when HDMI display
    is used as primary instead of LCD panel.

    Based on patch from Mark Tyler.

    Rebased from p-ics-mr1:
    9dd8ccd Support HDMI as primary display

    Change-Id: Idd239a562bfc486e128b268fa31ced53412bba3a
    Signed-off-by: Mykola Ostrovskyy <mykola@ti.com>
    Signed-off-by: Muralidhar Dixit <murali.dixit@ti.com>
    Signed-off-by: Tony Lofthouse <a0741364@ti.com>

commit a3825d82a12fb37ef674a3970ee6f8d0d76da587
Author: Dandawate Saket <dsaket@ti.com>
Date:   Thu Apr 12 11:55:52 2012 +0530

    hwc: Add support for FB scaling and cloning

    Patch contains following features
    1)Large frame buffer support:
         Transformation matrix for LCD and HDMI added
         to ensure correct composition and renderring
         of all UI layers
         Added support for overlay distrubution based
         on FB size and target display
    2)Default HDMI display support
         Support for default HDMI display selection.
         Added HDMI best mode selection on HPD

    Rebased from p-ics-mr1:
    96ad001 hwc: Add support for FB scaling and cloning

    Change-Id: Ia6f06d5e149656c4d79ac2d3983211a253bb3969
    Signed-off-by: Lajos Molnar <molnar@ti.com>
    Signed-off-by: Muralidhar Dixit <murali.dixit@ti.com>
    Signed-off-by: Dandawate Saket <dsaket@ti.com>

commit 62b870e5be867f00f841a74af85f0845902aa29b
Author: codeworkx <codeworkx@cyanogenmod.org>
Date:   Sun Dec 16 11:06:53 2012 +0100

    hwc: fix timing issue with vsync sysfs loop

    Change-Id: I6e0307e0fd5ea84748ddb580062b21f697512603

commit 53cacd86d64639e7f0d722c49b45caacf96b8594
Author: codeworkx <codeworkx@cyanogenmod.org>
Date:   Sat Dec 1 13:02:41 2012 +0100

    hwc: support vsync notification via sysfs

    Change-Id: Ie2172b5fb2e8595136f6ccb28abd9f8ce89a526f

Change-Id: Iefad6864e1a70a94589f68ca66c85de48f5e5c32