aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/cpu-freq/governors.txt
diff options
context:
space:
mode:
authorChristopher Kenna <cjk@cs.unc.edu>2012-09-28 13:46:28 -0400
committerChristopher Kenna <cjk@cs.unc.edu>2012-09-28 14:50:15 -0400
commitdaa22703f14c007e93b464c45fa60019a36f546d (patch)
treea1a130b6e128dc9d57c35c026977e1b4953105e1 /Documentation/cpu-freq/governors.txt
parent5aa287dcf1b5879aa0150b0511833c52885f5b4c (diff)
Apply k4412 kernel from HardKernel for ODROID-X.
Diffstat (limited to 'Documentation/cpu-freq/governors.txt')
-rw-r--r--Documentation/cpu-freq/governors.txt38
1 files changed, 38 insertions, 0 deletions
diff --git a/Documentation/cpu-freq/governors.txt b/Documentation/cpu-freq/governors.txt
index e74d0a2eb1c..51b1cd360c3 100644
--- a/Documentation/cpu-freq/governors.txt
+++ b/Documentation/cpu-freq/governors.txt
@@ -28,6 +28,7 @@ Contents:
282.3 Userspace 282.3 Userspace
292.4 Ondemand 292.4 Ondemand
302.5 Conservative 302.5 Conservative
312.6 Interactive
31 32
323. The Governor Interface in the CPUfreq Core 333. The Governor Interface in the CPUfreq Core
33 34
@@ -193,6 +194,43 @@ governor but for the opposite direction. For example when set to its
193default value of '20' it means that if the CPU usage needs to be below 194default value of '20' it means that if the CPU usage needs to be below
19420% between samples to have the frequency decreased. 19520% between samples to have the frequency decreased.
195 196
197
1982.6 Interactive
199---------------
200
201The CPUfreq governor "interactive" is designed for latency-sensitive,
202interactive workloads. This governor sets the CPU speed depending on
203usage, similar to "ondemand" and "conservative" governors. However,
204the governor is more aggressive about scaling the CPU speed up in
205response to CPU-intensive activity.
206
207Sampling the CPU load every X ms can lead to under-powering the CPU
208for X ms, leading to dropped frames, stuttering UI, etc. Instead of
209sampling the cpu at a specified rate, the interactive governor will
210check whether to scale the cpu frequency up soon after coming out of
211idle. When the cpu comes out of idle, a timer is configured to fire
212within 1-2 ticks. If the cpu is very busy between exiting idle and
213when the timer fires then we assume the cpu is underpowered and ramp
214to MAX speed.
215
216If the cpu was not sufficiently busy to immediately ramp to MAX speed,
217then governor evaluates the cpu load since the last speed adjustment,
218choosing the highest value between that longer-term load or the
219short-term load since idle exit to determine the cpu speed to ramp to.
220
221The tuneable values for this governor are:
222
223min_sample_time: The minimum amount of time to spend at the current
224frequency before ramping down. This is to ensure that the governor has
225seen enough historic cpu load data to determine the appropriate
226workload. Default is 80000 uS.
227
228go_maxspeed_load: The CPU load at which to ramp to max speed. Default
229is 85.
230
231timer_rate: Sample rate for reevaluating cpu load when the system is
232not idle. Default is 30000 uS.
233
1963. The Governor Interface in the CPUfreq Core 2343. The Governor Interface in the CPUfreq Core
197============================================= 235=============================================
198 236