MSM HOTPLUG: Suspend Functions re write in much clean way by Alucard24!

Now me and Alucard24 in full sync! join us :)

https://github.com/Alucard24/Alucard-Kernel-jfltexx/commit/c996594d30eb1fd567d82745b4b12c80d90df577
ARM: Don't dump vmalloc addresses with show_data()

Memory-mapped IO address spaces cannot be safely dumped at will.
Some addresses may not be available (clocked, powered) at all times,
and may result in hangs or bus decode errors if accessed. Other
registers that are accessible may have read side-effects, and dumping
them may have adverse affects on stability or the functionality of
the affected peripheral.

Be safe, and skip dumping such addresses altogether.

CRs-Fixed: 625442
Change-Id: I4cfa75f027ededf841a0240715af0db385857cbe
Signed-off-by: Matt Wagantall <mattw@codeaurora.org>
Signed-off-by: Vignesh Radhakrishnan <vigneshr@codeaurora.org>
ARM: Improve vmalloc address checking in show_data()

There is an unhandled corner case with the current check
which has recently been hit. The nbytes argument may be
large enough for the range being dumped to cross a
boundary between page-table mappings, and dump addresses
which are vmalloc'd in the neighboring mapping.

Check every address being dumped to see if its vmalloc'd,
not just the address passed to show_data().

CRs-Fixed: 625442
Change-Id: I255b093808177321f5202dcacea337ee333bfc63
Signed-off-by: Matt Wagantall <mattw@codeaurora.org>
MSM HOTPLUG: Fixes for correct defines for POWERSUSPEND.

Alucard :) please drink more coffee at night builds :)
Build Script: More coreect way to build with max CPU threads.
MSM HOTPLUG: Corrected wake/suspend function using lcd notify.

If kernel has no powersuspend or early suspend, then it's will use

LCD Notify code, if kernel dont have that too... well BUMMER!
Go and merge one of the suspend/wake codes.

Thanks to @franciscofranco for correct lcd notify code.
msm: hotplug: Initialize and terminate mutex properly

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
INTELLI HOTPLUG: Bump to v3.6 after merging with neobuddy89 source

* Restore input_event function.
* Move boost functionality to input_event, makes sense.
* Initialize and terminate mutex properly.
* Add minimum interval to prevent recurring boost.
* Revert create_singlethread_workqueue and use High Priority again.
* Merge code style from neobuddy89
* Merge new controls and defines from neobuddy89

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
MSM HOTPLUG: Use only screen touch event for boost code.
MSM HOTPLUG: ZIP suspend/resume code for all 3 mods + add missing code.

*No need to waste code lines for same thing.
*Add missing msm_hotplug_resume for early suspend mode.
mmc: core: continue to wait, when unblocked by signal

Mmc thread is waiting for one of following events occurs:
- current running request completion (is_done_rcv)
- new request notification arrived (is_new_req)
- urgent request notification arrived (is_urgent)
or the thread received a signal. In this case none of described events
happened.

This change process the case, when mmc thread was unblocked from wait by
signal, for example system shutdown flow.

Signed-off-by: Konstantin Dorfman <kdorfman@codeaurora.org>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
test: fixup defconfigs
msm: lpm_levels: Fix incorrect computation of next wakeup time

The next event timer wakeup was incorrectly computed when the hard timer
event doesn't exist. Fix by ensuring the next wakeup is computed only
when a timer event is valid

Change-Id: I40c1f372f84d8f43b2101e37dcfb592193d4b2e0
Signed-off-by: Mahesh Sivasubramanian <msivasub@codeaurora.org>
cpuboost: Add hotplug boosting

If we decide to hotplug a core then we are making a strong
statement that we think that the system load is high.  Let's
have faith in our hotplug driver(s) and boost the cpufreq
when we are hotplugging cores.

[myfluxi: shorter boost, minor style changes]

Change-Id: Id35bae6c27c39097c7aca70eebf1498ed0c3dfdc
msm-camera: Avoid adding top up to calulated ab/ib for single stream.

Avoiding topup for ab/ib for single stream

Change-Id: Ie6fb6716ea1b30604d801936bea3da5a96d8a6fc
Signed-off-by: Chandan Gera <cgera@codeaurora.org>
defconfig: cleanup knockcode
Makefile: edit optimization flags
drivers: slimbus: initial overclocking of slimbus

Increase root freq from 11 (24.526MHz) to 31 max (27+MHz) which is the largest it will take.
Increase clock gear from 7 to 10 (max again)

This means SLIMbus will use its maximum potential to give the best audio quality for the hardware. Takes advantage of both hardware and the mods from zeroinfinity, also opening the door for more things that were previously limited by this. Researched and experimented by ZeroInfinity and Poondog

Signed-off-by: poondog <markj338@gmail.com>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
slimbus: Provide framer-booted notification to slimbus device drivers

When slimbus resets (due to bus reset sequence, or after it shuts down
and comes up), framer boots up and starts clocking the bus.
Devices on the bus may be in undefined state at that time. Callback
is provided to slimbus device drivers so that controller can report
framer-booted notification so that drivers can take necessary action
to put devices in reset state so that they can acquire sync, report
present, and be operational.

Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
slim_msm: ngd: Return success for channel removal during ADSP SSR

Slimbus master component resides on ADSP when this driver is used.
Wehn ADSP restarts, slimbus component goes down and bus is not
operational until it comes back up. During restart, slimbus clients
are notified since their device goes down, and the clients remove
channels and/or disconnect ports. Since bus is not operational,
return success for channel removal/port disconnection calls so that
the channel, port state is consistent with HW (not active, removed)

Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>