Revert "Allow using low charge from USB HUB"

This reverts commit 58729ae9feb3a5b655dfddb569f48cde0a15b83d.
ONDEMAND: remove not working input_boost
Update ONDEMAND with new input booster function.
cpufreq: cpu-boost: Use hotplug thread infrastructure

Before this patch, thread migration ran in uninterruptible threads.
Use the relatively new hotplug thread infrastructure with parked
threads to reduce cpu load (x4).
cpufreq: cpu-boost: Fix queue_delayed_work_on() race with hotplug

Calling queue_delayed_work_on() on a CPU that's in the process of getting
hotplugged out can result in that CPU infinitely looping in
msm_pm_wait_cpu_shutdown(). If queue_delayed_work_on() is called after the
CPU is hotplugged out, it could wake up the CPU without going through the
hotplug path and cause instability. To avoid this, make sure the CPU is and
stays online while queuing a work on it.

Change-Id: I1b4aae3db803e476b1a7676d08f495c1f38bb154
Signed-off-by: Saravana Kannan <skannan@codeaurora.org>

Conflicts:
	drivers/cpufreq/cpu-boost.c
cpufreq: cpu-boost: Don't register for cpufreq notifiers too early

The cpufreq notifiers should be registered only after all the data
structures used in the notifier callbacks have been initialized. So, move
the cpufreq notifier registration to a later point in the init function.

Change-Id: I043ab5bc0ebb98164c40549fe151a8d801c8c186
Signed-off-by: Saravana Kannan <skannan@codeaurora.org>
cpufreq: cpu-boost: Increase sync thread policy and priority

More or less all cpufreq related threads run in a high priority.

Also, CMs patch series was somehow out of sync and incomplete,
readd the unchanged policy update to source cpu bit. And readd
the check for a possible corner case in try_to_wake_up() that
was already missing before.
CPU-BOOST: add description for input event value.
cpufreq: cpu-boost: Remove unused waitqueue
ONDEMAND: Remove no longer used input booster code. it's in CPU BOOST.
CPU BOOST: set default boost freq to 960Mhz for 40ms.
msm: hotplug: Optimize latencies

Before this patch it took the algorithm too long to
react on sudden load spikes, although only noticable
in benchmarks. We would cycle 5-6 times until the
buffer average was finally high enough to trigger a
new target.  Improve latencies by instantly onlining
all cpus if current load on any cpu is above a certain
threshold.

fast_lane_load should not be higher than 78 as load
per cpu won't be above this value in our metric.

First cycle in hackbench
Before: 1.253sec
After: 0.796sec
INTERACTIVE: Full sync with @myfluxi build. + adapt to my tree.

This gov was very old in my branch as i dont use it as my gov
But some of my users use it.
So it's best to have updated version from one of the best DEVS around :)

Thanks for all myfluxi.
CPU BOOST: use 1574400 Freq for input boost. much better.
ONDEMAND: Allow Input Boost when SLOW_UP is used. + tuning. + restores.

Restored control for sync_freq + optimal_freq they = 960000 by default.