cpufreq: Add/Delete cpu GOVs & Set smartmax to default
block: Add/Delete IO schedulers & Set fiops to default

Conflicts:

	block/Kconfig.iosched
	block/Makefile
	block/fiops-iosched.c
cpu/gpufreq: Add CPU/GPU down/overclock
gee_defconfig: Set MIN cpufreq to 270MHz
arm: mach-msm: Add missed Kconfig's overclock option
board-mako-display: Fix dirty mako's default gamma settings
board-mako-display: Adjust gamma
Add USB force fast charging - From MikeEx kernel_msm

-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
franciscofranco/mako@5a8a4c8

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

https://github.com/MikeEx/kernel_msm/commit/e48ecaf3cf341bcc01388cfb7e5394f79f73602f#diff-180da13bbfd8174f79be4102fb423b61R50

Conflicts:

	arch/arm/mach-msm/Kconfig
	arch/arm/mach-msm/Makefile
gee_defconfig: Fix LOCALVERSION to CM
Add MSM_SLEEPER - From flar2/ElementalX-m7-4.0
flar2/ElementalX-m7-4.0@c27ade9
sound: Update faux sound to v3.5 - Thanks to faux123
sound control: Update faux sound to v3.6 - Thanks to faux123
fs: Add dynamic_fsync by faux123 - From MikeEx kernel_msm
Revert "msm: intelli_plug: add new hotplug driver from Faux123 Kernel - v3.7"

This reverts commit ca948911dda873f19b7a2e6ee5ef945a5be7c64b.
hotplug: Add intelli-plug 3.8 - Thanks to faux123

Conflicts:

	kernel/sched/sched.h
msm_mpdecision: Disable kernel side mpdecision
gee_defconfig: Add/Disable some of options
sync: don't block the flusher thread waiting on IO - From MikeEx kernel_msm

When sync does it's WB_SYNC_ALL writeback, it issues data Io and
then immediately waits for IO completion. This is done in the
context of the flusher thread, and hence completely ties up the
flusher thread for the backing device until all the dirty inodes
have been synced. On filesystems that are dirtying inodes constantly
and quickly, this means the flusher thread can be tied up for
minutes per sync call and hence badly affect system level write IO
performance as the page cache cannot be cleaned quickly.

We already have a wait loop for IO completion for sync(2), so cut
this out of the flusher thread and delegate it to wait_sb_inodes().
Hence we can do rapid IO submission, and then wait for it all to
complete.

Effect of sync on fsmark before the patch:

FSUse%        Count         Size    Files/sec     App Overhead
.....
0       640000         4096      35154.6          1026984
0       720000         4096      36740.3          1023844
0       800000         4096      36184.6           916599
0       880000         4096       1282.7          1054367
0       960000         4096       3951.3           918773
0      1040000         4096      40646.2           996448
0      1120000         4096      43610.1           895647
0      1200000         4096      40333.1           921048

And a single sync pass took:

real    0m52.407s
user    0m0.000s
sys     0m0.090s

After the patch, there is no impact on fsmark results, and each
individual sync(2) operation run concurrently with the same fsmark
workload takes roughly 7s:

real    0m6.930s
user    0m0.000s
sys     0m0.039s

IOWs, sync is 7-8x faster on a busy filesystem and does not have an
adverse impact on ongoing async data write operations.

Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

https://github.com/MikeEx/kernel_msm/commit/d4797348c70dd90fae6b11d26bdc62b1c035d0bc
ALSA: usb-audio: Fix the mixer control range limiting issue - From AK-xGenesis Kernel

ALSA: usb-audio: Fix the mixer control range limiting issue
- mixer_ctl_set() function is limiting the volume level
to particular range. This results in incorrect initial
volume setting for that device.
- In USB mixer while calculating the dBmin/dBmax values
resolution factor is hardcoded to 256 which results in
populating the wrong values for dBmin/dBmax.
- Fix is to use appropriate resolution factor while
calculating the dBmin/dBmax values.

CRs-Fixed: 515012
Prev-Change-Id: I502355af66f850bb65380c27333c3341fa43a947
Signed-off-by: Deepa Madiregama <dmadireg@codeaurora.org>

Change-Id: I79c14014ad6828a802f6978b796d8a4a91c87e46
ext4: speed up truncate/unlink by not using bforget() unless needed - From AK-xGenesis

Do not iterate over data blocks scanning for bh's to forget as they're
never exist. This improves time taken by unlink / truncate syscall.
Tested by continuously truncating file that is being written by dd.
Another test is rm -rf of linux tree while tar unpacks it. With
ordered data mode condition unlikely(!tbh) was always met in
ext4_free_blocks. With journal data mode tbh was found only few times,
so optimisation is also possible.

Unlinking fallocated 60G file after doing sync && echo 3 >
/proc/sys/vm/drop_caches && time rm --help

X86 before (linux 3.6-rc4):
# time rm -f test1
real    0m2.710s
user    0m0.000s
sys     0m1.530s

X86 after:
# time rm -f test1
real    0m0.644s
user    0m0.003s
sys     0m0.060s

MIPS before (linux 2.6.37):
# time rm -f test1
real    0m 4.93s
user    0m 0.00s
sys     0m 4.61s

MIPS after:
# time rm -f test1
real    0m 0.16s
user    0m 0.00s
sys     0m 0.06s

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Signed-off-by: Andrey Sidorov <qrxd43@motorola.com>
Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>