From 5c0f07b1fe37f724146e5dbd5a98e7753a119e2a Mon Sep 17 00:00:00 2001
From: Allen Martin <amartin@nvidia.com>
Date: Thu, 30 Jun 2011 23:54:07 -0700
Subject: [PATCH 487/696] Documentation: cpufreq: add description of timer_rate

Add description of timer_rate tunable and clean up some
typos.

Change-Id: I4b96a36aad51eed3bef0ee5f571dc6e0a94c8dd9
Signed-off-by: Allen Martin <amartin@nvidia.com>
---
 Documentation/cpu-freq/governors.txt |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/Documentation/cpu-freq/governors.txt b/Documentation/cpu-freq/governors.txt
index e891e51..51b1cd3 100644
--- a/Documentation/cpu-freq/governors.txt
+++ b/Documentation/cpu-freq/governors.txt
@@ -215,10 +215,10 @@ to MAX speed.
 
 If the cpu was not sufficiently busy to immediately ramp to MAX speed,
 then governor evaluates the cpu load since the last speed adjustment,
-choosing th highest value between that longer-term load or the
+choosing the highest value between that longer-term load or the
 short-term load since idle exit to determine the cpu speed to ramp to.
 
-The tuneable value for this governor are:
+The tuneable values for this governor are:
 
 min_sample_time: The minimum amount of time to spend at the current
 frequency before ramping down. This is to ensure that the governor has
@@ -228,6 +228,8 @@ workload.  Default is 80000 uS.
 go_maxspeed_load: The CPU load at which to ramp to max speed.  Default
 is 85.
 
+timer_rate: Sample rate for reevaluating cpu load when the system is
+not idle.  Default is 30000 uS.
 
 3. The Governor Interface in the CPUfreq Core
 =============================================
-- 
1.7.1


