summaryrefslogtreecommitdiff
path: root/Documentation/cpu-freq
diff options
context:
space:
mode:
authorJunjie Wu <junjiew@codeaurora.org>2015-09-18 18:13:01 -0700
committerDavid Keitel <dkeitel@codeaurora.org>2016-03-23 21:25:28 -0700
commit1a76fe2389d173d6bbe4fd12e078205fe0095a4c (patch)
tree5376a3ee34ac98595cf7ec925c92ef4acaec893c /Documentation/cpu-freq
parenta81be0508668e4a7c044cb34e1188abeed28b158 (diff)
cpufreq: interactive: Delay evaluation of notification by 1ms
Multiple migrations can happen together within short period if scheduler is re-arranging a few tasks. In this case, it's only useful to change frequency at the end of all migrations. Delay handling of scheduler notification by 1ms. Change-Id: I9ee7b1e93ce57c28919b5609c40dcde9bd14abed Suggested-by: Saravana Kannan <skannan@codeaurora.org> Signed-off-by: Junjie Wu <junjiew@codeaurora.org>
Diffstat (limited to 'Documentation/cpu-freq')
-rw-r--r--Documentation/cpu-freq/governors.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/cpu-freq/governors.txt b/Documentation/cpu-freq/governors.txt
index d39d6818907d..9a92412d44a1 100644
--- a/Documentation/cpu-freq/governors.txt
+++ b/Documentation/cpu-freq/governors.txt
@@ -312,9 +312,9 @@ information such as migration. If non-zero, this also implies governor
sampling windows are aligned across CPUs, with same timer_rate,
regardless what align_windows is set to. Default is zero.
-use_migration_notif: If non-zero, reevaluate CPU's frequency
-immediately after receiving notification from scheduler. If zero,
-ignore scheduler notification. Default is zero.
+use_migration_notif: If non-zero, schedule hrtimer to fire in 1ms
+to reevaluate frequency of notified CPU, unless the hrtimer is already
+pending. If zero, ignore scheduler notification. Default is zero.
max_freq_hysteresis: Each time freq evaluation chooses policy->max,
next max_freq_hysteresis is considered as hysteresis period. During