Revert "CK3 tweaks (Credits to Con Kolivas)"

This reverts commit 93d552062de81a49fba9d4f0bb11639ae1d5884e.
Revert "mm: change initial readahead window size calculation"

This reverts commit 5f6f3bee108de5bee5d0c817b35f6d0787ac3223.
Revert "block: row-iosched idling triggered by readahead pages"

This reverts commit 66f5e50c63e3237face84df4b21467618a5429ed.
Revert "mm: pass readahead info down to the i/o scheduler"

This reverts commit 1e59c91f2aa7eb9719db490e2342319022c22cf1.
mmc: msm_sdcc: check for pending_resume in SDCC system suspend

If system comes out of suspend, msmsdcc_pm_resume() sets the
host->pending_resume flag if the SDCC wasn't runtime suspended.
Now if the system again goes to suspend without any SDCC activity
then host->pending_resume flag will remain set which may cause the SDCC
resume to happen first and then suspend.

To avoid this unnecessary resume/suspend, make sure that pending_resume
flag is cleared before calling the msmsdcc_runtime_suspend().

CRs-Fixed: 438081
Change-Id: I2b667bec704f938a532d4780dd9b7937e2eb12c7
Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
msm: cpufreq: Ensure cpufreq change happens on corresponding CPU

Checking the cpus_allowed mask of the current thread before changing the
frequency doesn't guarantee that the rest of the execution will continue
on the same CPU. The only way to guarantee this is to schedule a work on
the specific CPU and also prevent hotplug of that CPU (already done by
existing code).

Change-Id: I51a02fcc777a47d3c16f2d83c47e96f2c59f7ae6
Signed-off-by: Saravana Kannan <skannan@codeaurora.org>
msm: cpufreq: Only apply driver limits for scaling_min/max_freq writes

When new values are written to scaling_min/max_freq sysfs files, the
current code applies all the limits imposed by various ADJUST and
INCOMPATIBLE notifiers handlers before storing them.

When the ADJUST and/or INCOMPATIBLE notifiers change their limits
frequently, this behavior makes it almost impossible for a
user/userspace process to store the scaling_min/max_freq limits
that go beyond the instantaneous limits imposed by the notifiers.
Since these sysfs nodes are typically meant to set limits that need
to be enforced for the foreseeable future, this is not a very user
friendly behavior.

So, change the behavior to only apply limits that are enforced by
the cpufreq driver. Typically, these are just the absolute limits
of the HW and don't change very often.

Change-Id: I1ccfaa2d1ee4ea595f882485d359dbdb407a0176
Signed-off-by: Deepak Katragadda <dkatraga@codeaurora.org>
msm: cpufreq: Relax constraints on "msm-cpufreq" workqueue
This workqueue is not used in memory reclaim paths, so the
WQ_MEM_RECLAIM flag is not needed. Additionally, there is no
need to restrict the queue to having one in-flight work item.
Remove these constraints.

Change-Id: I9edde40917d3ec885ce061133de20680634321d0
Signed-off-by: Matt Wagantall <mattw@codeaurora.org>

Conflicts:
	arch/arm/mach-msm/cpufreq.c
Revert "acpuclock: Change to 162mhz min freq and add 270mhz between 162mhz and 384mhz"

This reverts commit 3b5d11ab8318231186d4a5e15dff8d64f339491c.
Revert "acpuclock: Fix Frequency Table"

This reverts commit 18e421271d41f3296b8703a416fbc51095bb0576.