vibrator function

Signed-off-by: flar2 <asegaert@gmail.com>

Conflicts:
	drivers/misc/pm8xxx-vibrator.c
S2W/DT2W/L2M/L2W

Signed-off-by: flar2 <asegaert@gmail.com>

Conflicts:
	drivers/input/touchscreen/synaptics_3200.c
	include/linux/synaptics_i2c_rmi.h
fix pocket detection

Signed-off-by: flar2 <asegaert@gmail.com>
Make dt2w more sensitive

Signed-off-by: flar2 <asegaert@gmail.com>
dt2w: enable only on the bottom part of screen

Signed-off-by: flar2 <asegaert@gmail.com>
fullscreen/halfscreen option and make it more sensitive

Signed-off-by: flar2 <asegaert@gmail.com>
fix logo2wake from deep sleep and remove some logspam

Signed-off-by: flar2 <asegaert@gmail.com>
redo algorithm and a few other touch ups

Signed-off-by: flar2 <asegaert@gmail.com>
fix wakelock

Signed-off-by: flar2 <asegaert@gmail.com>
Add sweep up to wake
S2W/L2W/DT2W: Make vibration more immediate when activated
Wake Gestures interface

This creates a new input devices (wake_gesture) and generates input events for several gestures while the screen is off:

00000001 -> sweep right
00000002 -> sweep left
00000003 -> sweep up
00000004 -> sweep down
00000005 -> doubletap
00000006 -> long press HTC logo

These input events can be used by userspace apps to perform custom actions for each gesture
wake gestures: fix l2m dependency, sweep over buttons, and multiple trigger
comment these out for now so it will build
clean up old wake options stuff
DRIVERS: SLIMBUS: some more tweaks:
Set ROOT_FREQ at 22, which is double what we had before. According to some documents this is what we want for optimium audio quality
Forcec SLIM_RATE to 44.1KHz and 48KHz instead of much lower values. This way it will be forced to run at these freqs to match the majority of audio files user will be playing.

ZeroInfinity/Poondog

Signed-off-by: ZeroInfinity <infinitezero345@gmail.com>
Signed-off-by: poondog <markj338@gmail.com>
clean up old blinking buttons code
disable old wake options in defconfig
msm: timer: Use 32768Hz GPT and SCLK on 8064 family

On 8064 SOC family, a dedicated XO is derived to support
sleep clock at 32768Hz unlike 8960 SOC family where TCXO
divider was used with effective freq. of 32765Hz.

CRs-fixed: 462079
Change-Id: I79142703c4ffac209f4dedeefebc235eeb8b140d
Signed-off-by: Jay Chokshi <jchokshi@codeaurora.org>
sched: reinitialize rq->next_balance when a CPU is hot-added
Reinitialize rq->next_balance when a CPU is hot-added.  Otherwise,
scheduler domain rebalancing may be skipped if rq->next_balance was
set to a future time when the CPU was last active, and the
newly-re-added CPU is in idle_balance().  As a result, the
newly-re-added CPU will remain idle with no tasks scheduled until the
softlockup watchdog runs - potentially 4 seconds later.  This can
waste energy and reduce performance.

This behavior can be observed in some SoC kernels, which use CPU
hotplug to dynamically remove and add CPUs in response to load.  In
one case that triggered this behavior,

0. the system started with all cores enabled, running multi-threaded
   CPU-bound code;

1. the system entered some single-threaded code;

2. a CPU went idle and was hot-removed;

3. the system started executing a multi-threaded CPU-bound task;

4. the CPU from event 2 was re-added, to respond to the load.

The time interval between events 2 and 4 was approximately 300
milliseconds.

Of course, ideally CPU hotplug would not be used in this manner,
but this patch does appear to fix a real bug.

Nvidia folks: this patch is submitted as at least a partial fix for
bug 1243368 ("[sched] Load-balancing not happening correctly after
cores brought online")

Change-Id: Iabac21e110402bb581b7db40c42babc951d378d0
Signed-off-by: Paul Walmsley <pwalmsley@nvidia.com>
Cc: Peter Boonstoppel <pboonstoppel@nvidia.com>
Reviewed-on: http://git-master/r/208927
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Peter Zu <pzu@nvidia.com>
Reviewed-by: Peter Boonstoppel <pboonstoppel@nvidia.com>
GVS: Gerrit_Virtual_Submit
Tested-by: Peter Zu <pzu@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>