USB: Set power supply online status to false after cable disconnect

During bootup, power supply online status is set to true in
qpnp_charger_probe() as soon as usb cable insert is detected by
PMIC without waiting for notification from USB driver.
Later when usb cable is disconnected before charger detection
mechanism starts, online status is not set to false by USB.
As part of cable disconnect, USB checks in msm_otg_notify_charger()
whether the cur_power is same as requested mA, if both are same
then USB does not call power_supply_set_online() to set it to false.

Fix the issue by setting power supply online status to false for
the scenario when usb cable is disconected during bootup before
charger detection mechanism is completed.

CRs-fixed: 634183
Change-Id: Ibd57a40c7364e13bb10870e9e6343224e01171d7
Signed-off-by: Saket Saurabh <ssaurabh@codeaurora.org>
cma: Drop the right mutex

The lock that was locked was cma->lock not cma_mutex. Drop
the right one when breaking out of the loop.

Change-Id: I0a1831b23613c5220795fe2a63f9db7439268c3f
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
cpufreq: ondemand: Increase sync thread policy and priority
Revert "cpufreq: cpu-boost: Introduce scheduler assisted load based syncs"

If you love memory corruption and kernel panics, this is something
for you! This reverts commit 7e80933724e8ff74b2297566847aa39395e64cbb.

Revert "cpufreq: cpu-boost: Make it less noisy"
This reverts commit ae9bd2f356c28972903d1b8ce6711388ee2b15c7.

Revert "sched: Call the notify_on_migrate notifier chain for wakeups as well"
This reverts commit 2e17f359e7a26a453f2bc9cdeca7c2d2137fe050.

Revert "sched: window-based load stats for tasks"
This reverts commit 8a23adc2e6bdfd60d6297a24aff0f2c4b5cfe808.

Revert "sched: Make scheduler aware of cpu frequency state"
This reverts commit 388a3b329227cd389339f5de9d5a15294b47f937.

Revert "cpufreq: cpu-boost: Handle wakeup hints received for foreground tasks"
This reverts commit faa2675cbd2cd01d1d15f0711aa64081390125be.
qcom-cpufreq: Block hotplug until cpufreq is ready

Hotplug before qcom-cpufreq is ready could lead to inconsistent CPU
clock state. Block hotplug by returning NOTIFY_BAD in hotplug callback
until qcom-cpufreq is probed.

Change-Id: I72a2f98c083c9b21b95ecafdb5a5be7a7682e842
Signed-off-by: Junjie Wu <junjiew@codeaurora.org>
qcom-cpufreq: Fix hotplug blocking logic

Change 2b63b10 qcom-cpufreq: Block hotplug until cpufreq is ready
intended to block hotplug until qcom-cpufreq driver has got all
clocks. However, its implementation still leaves a small window when
CPU 0 has got its clock but others haven't. If a hotplug happens on
another CPU that doesn't have its clock pointer, refcount of that CPU
clock will again be wrong.

Fix the issue by introducing a ready flag.

Change-Id: I1e05b063b0584088f717b82709a3f1d55bc6561b
Signed-off-by: Junjie Wu <junjiew@codeaurora.org>