cpufreq: ondemand: set screen off max freq to 2.2ghz

*restore stock behavior
cpufreq: don't go above 2.27ghz when adding device
cpufreq: make thermal-engine play nicely with OC

* not perfect yet but should do for now

Conflicts:

	drivers/cpufreq/cpufreq.c
clock-krait/cpufreq: custom voltage control v1

* TODO: control only available frequencies
cpufreq: set policy max properly

* how did this ever work?
cpufreq: interactive: while overclocking, favor stock max unless load => 99
cpufreq: interactiveX V4: limit max freq when screen off

screen_off_max configurable via sysfs - default 2.27ghz
cpufreq: interactive: delete timers for GOV_START

Make sure that timers cpu_timer and cpu_slack_timer
deactivated before addition of new.

Change-Id: If31c4049606871df6f00efdc24b1d713c86a6f69
Signed-off-by: Shridhar Rasal <srasal@nvidia.com>
Signed-off-by: Bharat Nihalani <bnihalani@nvidia.com>
Git-commit: b430123367e78a6557bac3cf1558bcb85193fb12
Git-repo: https://android.googlesource.com/kernel/common/
[mattw@codeaurora.org: resolved trivial context conflict]
Signed-off-by: Matt Wagantall <mattw@codeaurora.org>
cpufreq: Sync on thread migration optimizations

When threads migrate between CPUs the destination CPU will temporarily
have a boosted frequency and the source CPU will have a residual higher
frequency even though the load could have just been reduced. To avoid
leaving CPUs at a high frequencies notify the source CPU after a thread
migration and make the interactive governor's timer reschedule
conditionally.

Change-Id: Id55055f2a116ca7ffd2a34dc3d0ec519c888a111
Signed-off-by: Patrick Cain <pcain@codeaurora.org>