Revert "Fix undefined reference to a 64bit function on ext4 stack in one of the latest 3.0.y patches."

This reverts commit c7baee4fe5c982e9a7589cf44ae6017a8304d8b2.
Revert "arm: mm: fix aligmnment may be unitialized var warning."

This reverts commit 08ca48ffac0fc00fa6a8d11a371c5a28cda1afe7.
Revert "ARM: 7592/1: nommu: prevent generation of kernel unaligned memory accesses"

This reverts commit a4667b86aaf84bdd9ea4c5dc98a6b83515492df0.
Revert "drivers/staging/android: backport timed_gpio form hammerhead"

This reverts commit d7ce96663a2b9288f80a77628218274f23aadc7b.
Revert "mm: slub: Default slub_max_order to 0"

This reverts commit 7a452dc768e89860bbf8f6e48e33cd93e599fea0.
Revert "ARM: 6998/2: kernel: use proper memory barriers for bitops"

This reverts commit 8aa059d76ef01d84d2371df9e42999f18f45f377.
Revert "mmc/core: increase limit_us"

This reverts commit 9ea022ee85a559996c5f7e58690b50fdeb05bb52.
Revert "mm, vmalloc: use well-defined find_last_bit() func"

This reverts commit d0ca6d156501ea367f01c6fa39b0a805b71fdde8.
Revert "mm, vmalloc: remove useless variable in vmap_block"

This reverts commit 594d5b77a5ceae2e09377854d80c7b3de68d91cb.
Removed Wheatly CPU Governor
cpufreq: Fix policy getting stuck when user & kernel min/max don't overlap

Every __cpufreq_set_policy starts with checking the new policy min/max has
some overlap with the current policy min/max. This works out fine until we
end up with the policy min/max being set to a range that doesn't overlap
with the user policy min/max. Once we get into this situation, the check at
the start of __cpufreq_set_policy fails and prevents us from getting out of
this state.

This only happens when one of the CPUFREQ_ADJUST/CPUFREQ_INCOMPATIBLE
notifiers called inside __cpufreq_set_policy pick a min/max outside the
range of user policy min/max.

The real intent of the check at the start of __cpufreq_set_policy is to
make sure userspace can't set user policy min > user policy max. Since
__cpufreq_set_policy always gets called only with current user policy
min/max except when the actual user space policy min/max is changed, we can
fix the issue by simply checking the new policy min/max against current
user policy min/max.

Change-Id: Iaac805825e64d7985c41fb9052bd96baacdf3d6f
Signed-off-by: Saravana Kannan <skannan@codeaurora.org>
Signed-off-by: Ka <k@ka.st>
Modified smartass2 DEFAULT_SLEEP_IDEAL_FREQ
Removed SmartAssH3 Governor
adjust Wi-Fi RSSI

Signed-off-by: Ka <k@ka.st>
adjust pmem driver for 720p

Signed-off-by: Ka <k@ka.st>
make pmem_adsp cached

Signed-off-by: Ka <k@ka.st>
board-semc_mogami.c: increase pmem_adsp size for 720p
increase sound volume

Signed-off-by: Ka <k@ka.st>
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>
Signed-off-by: Ka <k@ka.st>
Staging: android: timed_gpio: Fix unreg order

Fix the order of unregister timed output device to avoid
use after free bug.

Change-Id: I7b1e51002f17e7cc277db6cf07188e96217ad13c
Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
Signed-off-by: Ka <k@ka.st>