Initial commit of VS98024A sources.
Use CyanogenMod's devtree tool.

Conflicts:
	arch/arm/configs/g2-vzw-perf_defconfig

Change-Id: I7506eae637078f97c2c6122e775093d4b58a2b07
Add bullshit device tree stubs.

LG's 4.2 aboot searches for

/soc/qcom,mdss_dsi_lgit_video
/soc/qcom,mdss_dsi_jdi_video
/soc/qcom,mdss_dsi_jdi_cmd
/soc/qcom,mdss_dsi_lgit_cmd

before booting the kernel; and it will explicitly fail to boot if they aren't
present, as defined somewhere in their aboot source. This will appease the
4.2 bootloader and allow us to boot a kernel built on 4.4 sources.

The 4.4 aboot will also append:
"mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_g2_lgd_cmd" to kernel's command line, so
adding the above to the BOARD_KERNEL_CMDLINE in the device folder is necessary
to get the panel to work. (Thanks to xda user garyd9 for pulling /proc/cmdline)

A big thank you to Dan Rosenberg (djrbliss) for loki (the exploit that allows
for custom boot images)
tspdrv: Add LG's timed_output based interface

Change-Id: I43383ad9e0ba4e0ba13837c0741885162cf40b63

 This is the 2nd commit message:

tspdrv: Make the timed state atomic

This should fix race conditions with fast bursts of short tones

Change-Id: I2c369da0a80dedebf7346613437d2b69d6a92c3c

 This is the 3rd commit message:

tspdrv: Add a sysfs control for timed vibrator strength

Change-Id: I66dec312e52a3c8834a93f6b8970c94a0d6af923

Conflicts:
	drivers/misc/tspdrv/ImmVibeSPI.c
lge_touch: Generate KEY_POWER events for wakeup gestures

Conflicts:
	drivers/input/touchscreen/lge_touch_core.c

Change-Id: I76950b6f920f48797379ddf1ff518253f6b6840b
lge_touch: Move gesture KEY_POWER event out of interrupt context

That's generally an awful idea, put it in the workqueue instead

Conflicts:
	drivers/input/touchscreen/lge_touch_core.c

Change-Id: I21974275363c6b83beb2795b11da05d718747be8
msm_ipc_router: Allow processes in the oncrpc group to use it freely

Instead of adding rild to the current catch-all net-raw group,
treat the oncrpc group as another catch-all.
Fix path.

Change-Id: Iedc64cb79e94595f14837ef0280e606bd602d9d9

Conflicts:
	arch/arm/configs/g2-vzw-perf_defconfig
Change led name for cm-11.0 device source compatibility.

Change-Id: I34a6ff18f6a0636000e42f520f781eabee2fae04
Remove unused configs.

Change-Id: I0bce3d76ee070e0ecb151b70bc6a14d5f346722f
bluesleep: Back out LGE_BLUESLEEP changes and add bluedroid support

Conflicts:
	drivers/bluetooth/bluesleep.c

Change-Id: If11e3cbed60d65eaba10e5b27f967aa34b49d91a
bluesleep: Fix L2 crash with host-initiated bluetooth connections
bluesleep: Remove remnants of LGE_BLUESLEEP

The patching of msm_serial_hs should make the clock workarounds
unnecessary
bluesleep: Reset the check timer interval to the original 10 seconds
Remove log spam.

Change-Id: I2f715844e9f416707a01f62abe0b81f05de0ec56
Enable BT LOCK

Change-Id: Idc413722cdb1ee94f46b3e334d2a08e9c8640a06
Don't build these tuners.

Change-Id: I51a1c6edd62f990cd8260635f6a30b2a6c1e80b9
lowmemorykiller: Account for highmem during kswapd reclaim

Currenlty most memory reclaim is done through kswapd.
Since kswapd uses a gfp mask of GFP_KERNEL, and because
the lowmemorykiller is zone aware, the lowmemorykiller will
ignore highmem most of the time.
This results in the lowmemorykiller being overly aggressive.

The fix to this issue is to allow the lowmemorykiller to
count highmem when being called by the kswapd if the lowmem
watermarks are satisfied.

Change-Id: I938644584f374763d10d429d835e74daa4854a38
Signed-off-by: Liam Mark <lmark@codeaurora.org>
ls980: fix path error

Signed-off-by: baked <travp624@gmail.com>