msm: msm_limiter: Improve routines

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com> (reverted from commit 077658f8d3a852ab6a218c5bd0273f209fb0aeed)
defconfig: Enable MSM Limiter (reverted from commit ebdc3885548ca9f7cbb69ed67d5c6571543b8f05)
msm_limiter: set default values (reverted from commit 0cfec1f1d2d5e1a626f6c3f87163669323399ebb)
msm: msm_limiter: introduction (reverted from commit e374e08d4db338e4011b633775b3a4dab7c2592b)
CPU: set max freq on cmdline
qcom-cpufreq: limit min and max cpu frequencies
msm-sleeper: limit max freq when screen is off

Signed-off-by: flar2 <asegaert@gmail.com>
defconfig: enable MSM Sleeper
diag: Reduce error message frequency

Some diag error messages are printed with high frequency. This
cause flooding of kernel logs. Rate limiting these messages will
help reading kernel logs.

Change-Id: I477ff2394116603a27d65948a60d3460c32572d1
CRs-fixed: 594186
Signed-off-by: Katish Paran <kparan@codeaurora.org>
msm: msm_bus: Suspected fix for deadlock

mutex is not released while checking for
null pdata which can lead to possible deadlock
condition.

Change-Id: I1dc3efd725df5bb75c96434a81d9a8f3f868cd0a
Signed-off-by: Alok Chauhan <alokc@codeaurora.org>
msm: kgsl: enable CPU IRQ while suspending context

Make sure that CPU interrupt is enabled before calling adreno
suspend_context when moving from NAP/SLEEP to SLUMBER state.
We send commands to GPU in adreno_drawctxt_switch() which will generate
GPU interrupt. Since CPU interrupt is not enabled, adreno_idle() will
fail because pending interrupt will not be served by CPU this causes
false GPU hang.

CRs-Fixed: 547813

Change-Id: Ia4b730b8f8cda1e820f571ffb7ddb00336ca1a8c
Signed-off-by: Gaurav Gagrani <ggagrani@codeaurora.org>
cpufreq: cpu-boost: allow enable/disable via sysfs
cpufreq: ondemand: disable cpu-boost when switched to ondemand

* ondemand and cpu-boost don't play nice together
mmc: core: Expose use_spi_crc module parameter in sysfs
gpu: msm: for higher priority you want to use nice level of -7

* not 7 which has an opposite effect.  I'm sure this was a CAF
mistake.

* thanks to myfluxi for spotting this
Bumped to R5