summaryrefslogtreecommitdiff
path: root/drivers/cpufreq
diff options
context:
space:
mode:
authorAlexander Clouter <alex@digriz.org.uk>2009-02-13 22:03:26 +0300
committerDave Jones <davej@redhat.com>2009-02-25 06:47:32 +0300
commita75603a084f1dd9a9558c8af95fc2acfc54f1021 (patch)
tree6b8369d6a60c8eb21ba9686def3d73548cc27974 /drivers/cpufreq
parent8e677ce83bf41ba9c74e5b6d9ee60b07d4e5ed93 (diff)
downloadlinux-a75603a084f1dd9a9558c8af95fc2acfc54f1021.tar.xz
[CPUFREQ] conservative: remove 10x from def_sampling_rate
AMD users get particular hit by this issue (bug 8081) as it caps at typically 90 seconds as the minimum period for a frequency change. Harsh eh? Years ago I borked this buy puting the 10x in the wrong place...I fix that by removing it altogether. Signed-off-by: Alexander Clouter <alex@digriz.org.uk> Signed-off-by: Dave Jones <davej@redhat.com>
Diffstat (limited to 'drivers/cpufreq')
-rw-r--r--drivers/cpufreq/cpufreq_conservative.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/cpufreq/cpufreq_conservative.c b/drivers/cpufreq/cpufreq_conservative.c
index c9bd0c55ad1e..2ecd95e4ab1a 100644
--- a/drivers/cpufreq/cpufreq_conservative.c
+++ b/drivers/cpufreq/cpufreq_conservative.c
@@ -599,7 +599,7 @@ static int cpufreq_governor_dbs(struct cpufreq_policy *policy,
latency = 1;
def_sampling_rate =
- max(10 * latency * LATENCY_MULTIPLIER,
+ max(latency * LATENCY_MULTIPLIER,
MIN_STAT_SAMPLING_RATE);
dbs_tuners_ins.sampling_rate = def_sampling_rate;