cpufreq: interactive: port latest from common/android-3.4
cpufreq: interactive: delete timers for GOV_START
from aosp-common/android-3.10
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>
___________________

cpufreq: interactive: Move definition of cpufreq_gov_interactive downwards
This moves definition of cpufreq_gov_interactive towards the bottom of file, so
that we don't have to add prototype of cpufreq_governor_interactive() in the
beginning of file.

Change-Id: I04bd1004954eb36502c5cd7e35d3d7274cddaf95
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
cpufreq: interactive: updates from CAF

Add a sampling_down_factor for max frequencies Rohit Gupta
Allow 1 ms error in above_hispeed_delay comparisons Rohit Gupta
sync freq feature for interactive governor Rohit Gupta
Reset floor_validate_time if busy at max for 100ms Rohit Gupta
Remove trace event from idle_start handler Rohit Gupta
Modifying sync_freq implementation Rohit Gupta
Use default min_sample_time if SDF is zero Rohit Gupta
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>
cpufreq: interactive: remove boostpulse related code
Boostpulse is supposed to decrease GUI latency (or improve GUI response)
but it is designed in the userspace and supposed to receive the pulse
signal from user-space service via sysfs interface. It is not a good idea
to place the latency sensitive code outside kernel. Removal of this code will
theoretically increase the efficiency of interactive governor since there wil
be fewer sysfs variables to monitor. Get rid of this useless feature since
touchboost service is disabled in the user space anyway.
cpufreq: interactive: fix compiling warnings

The gcc warns like:

  cpufreq_interactive.c:745:6: warning: operation on 'ret' may be
undefined [-Wsequence-point]

It was introduced by commit cf0fad49d17cb8273ce555dd5b7afab67d7923bf.

Since sprintf(...) just return 1 (one character) in this case, ret
should not changed.
Just discarding the result of sprintf(...) leads to the result that
the committer of cf0fad49d17cb8273ce555dd5b7afab67d7923bf wants.

Change-Id: Ifed1cef6d6a31c3ed23dad03a567b3b9eddf3a57
Signed-off-by: Chih-Wei Huang <cwhuang@android-x86.org>
Signed-off-by: Dave Daynard <nardholio@gmail.com>
defconfig: remove debugging