Update defconfigs

Signed-off-by: kecinzer <kecinzer@gmail.com>
Mako (absolute) Voltage control.

This started out as just including the existing work of someone else.
But that was so obfuscated and needlessly moved in sysfs, i turned it into the type control
we have on NP, meaning same sysfs location and output formatting.
Since the various kernels range from no preUV to different levels of UV it is best to encourage the user
to think in absolute voltages.
"I can UV -150 on kernel X! Really? Odd, i can only UV kernel Y -50mV!"
Kernel X has no preUV, kernel Y has 100mV preUV, so they both run the same.
This is needlessly confusing to users.

Talking in absolutes, users will get a better understanding of "what the other guy's" device is capable of.
Sticking to a common sysfs location and to the common absolute voltage is thus the right thing to do.

This seems to work now as it should.

This is heavily based on coolbho3k's NP patch. from Paul's mess we might have a few function names, but not the contents.
This is not his, if he claims otherwise, he can go fuck himself.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>

Conflicts:
	drivers/cpufreq/cpufreq.c
USB force fast charging

-Use base from Chad Froebel <chadfroebel@gmail.com> so we continue to
use the same generic sysfs mechanism

-Referenced franco's git for drivers/usb/otg/msm_otg.c changes
https://github.com/franciscofranco/mako/commit/5a8a4c8e23c7e1df39c740b9ce1d5dda20b0ede3

Off by default

Turn on:
echo 1 > /sys/kernel/fast_charge/force_fast_charge

Turn off:
echo 0 > /sys/kernel/fast_charge/force_fast_charge

Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>

Conflicts:
	arch/arm/mach-msm/Kconfig
	arch/arm/mach-msm/Makefile
board: flo: regulator: decrease regulator to allow for lower CPU voltages.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
msm: tsens8960: patch by @showp-1984 to enable all sensors.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
cpufreq: ondemand: fix a bug that when a user selected a max frequency that was equal to sync_freq or optimal_freq then the device would be stuck on that frequency until changing to other frequency or manually rebooted.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
drivers: input: fix the report that the user is touching the display for my touch_boost implementation on interactive governor.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
sound_control: add basic sound control.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>

Conflicts:
	drivers/misc/Makefile
sound_control: update how the new values get applied writing and reading them directly from the tabla registries. This will fix the breakage caused by 4.3.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
sound_control: just some cosmetic changes.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>
drivers: input: add a mechanism to wake the device by either double tapping the display or swipping from wherever you want. The device deep sleeps but the digitizer is still powered on, otherwise it couldn't detect touch events. Battery usage should be little to minimal, but I haven't ran any numbers.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>

Conflicts:
	drivers/input/touchscreen/lge_touch_core.c
drivers: input: major improvements on the doubletap to wake feature.

Signed-off-by: Francisco Franco <franciscofranco.1990@gmail.com>