msm: hotplug: Refactor lcd notifier callback

* Use Motorola's panel notifier implementation

Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
ramdisk: Tune msm_hotplug

Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
ghost: Set max CPUs to 2

Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
msm: hotplug: Remove duplicate get_cpu_idle_time function

Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
cpufreq: interactive: don't skip waking up speedchange_task if target_freq > policy->cur

When __cpufreq_driver_target() in speedchange_task failed for some reason, the
policy->cur could be lower than the target_freq. The governor misses to change
the target_freq if the target_freq is equal to the next_freq at the next sample
time.

Added a check to prevent the CPU to stay at the speed that is lower than the
target_freq for long duration.

Change-Id: Ibfdcd193b8280390b8f8374a63218aa31267f310
Signed-off-by: Minsung Kim <ms925.kim@samsung.com>
cpufreq: interactive: prevents the frequency to directly raise above the
hispeed_freq from a lower frequency.

When the load was below go_hispeed_load, there is a possibility that
choose_freq() would return a frequency which would be higher than the
hispeed_freq. According to the policy we should first jump to the
hispeed_freq, stay there for above_hispeed_delay and then be allowed to
raise higher than that.

Added a check to prevent the frequency to be directly raised to
something higher than the hispeed_freq.

Change-Id: Icda5d848dd9beadcc18835082ddf269732c75bd0
Signed-off-by: Ruchi Kandoi <kandoiruchi@google.com>
[zwliew: Backport to Linux 3.4]
Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
msm: rq_stats: Calculate load based on current freq limit

We are not using rq_stats any more so this commit is just for the
sake of completeness.  Prior to this patch, load has been calculated
based on an initial value of policy.cpuinfo.max_freq. This value may
change for several reasons: userspace settings, thermal throttling
(hello hammerhead!) or extended frequency tables where the absolute
maximum level is often not used during regular operations. This
results in unreliable calculations. Consider current policy.max to
fix this behaviour.

Conflicts:
	arch/arm/mach-msm/msm_rq_stats.c
Revert "msm:rq_stats: Register for Cpufreq policy notification"

This reverts commit 6b1e7c36e2d8dc0d706353414a3733292e6b73f2.

Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
msm: rq_stats: Disable hotplug and stats by default

Userspace closed source mpdecision binary is nessecary for PowerHAL to work.
As it depends on rq_stats, let's at least disable hotplugging and stats
collection by default. /sys/devices/system/cpu/cpu0/rq-stats/hotplug_disable
is now writable, so hotplug can be reenabled.

Also, add some bits related to current cpu policy.