|author||Stratos Karafotis <email@example.com>||2013-03-05 22:06:29 +0000|
|committer||Rafael J. Wysocki <firstname.lastname@example.org>||2013-04-01 01:11:35 +0200|
cpufreq: conservative: Fix sampling_down_factor functionality
sampling_down_factor tunable is unused since commit 8e677ce83bf41ba9c74e5b6d9ee60b07d4e5ed93 (4 years ago). This patch restores the original functionality and documents the tunable. Signed-off-by: Stratos Karafotis <email@example.com> Acked-by: Viresh Kumar <firstname.lastname@example.org> Signed-off-by: Rafael J. Wysocki <email@example.com>
Diffstat (limited to 'Documentation/cpu-freq')
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/cpu-freq/governors.txt b/Documentation/cpu-freq/governors.txt
index c7a2eb8450c2..4dfed30b7fda 100644
@@ -191,6 +191,12 @@ governor but for the opposite direction. For example when set to its
default value of '20' it means that if the CPU usage needs to be below
20% between samples to have the frequency decreased.
+sampling_down_factor: similar functionality as in "ondemand" governor.
+But in "conservative", it controls the rate at which the kernel makes
+a decision on when to decrease the frequency while running in any
+speed. Load for frequency increase is still evaluated every
3. The Governor Interface in the CPUfreq Core