cpufreq: conservative: Allow down_threshold to take values from 1 to 10
authorTomasz Wilczyński <twilczynski@naver.com>
Sun, 11 Jun 2017 08:28:39 +0000 (17:28 +0900)
committerRaspbian kernel package updater <root@raspbian.org>
Sun, 23 Jul 2017 03:00:16 +0000 (03:00 +0000)
commitdcd295f439ce3aa5451677433620fea9d9b57c37
tree09eec1af36e0b7080a9537b0d9f6e3e9a1e2c83f
parent373be609c83a123f481d071663914faa577a0d26
cpufreq: conservative: Allow down_threshold to take values from 1 to 10

commit b8e11f7d2791bd9320be1c6e772a60b2aa093e45 upstream.

Commit 27ed3cd2ebf4 (cpufreq: conservative: Fix the logic in frequency
decrease checking) removed the 10 point substraction when comparing the
load against down_threshold but did not remove the related limit for the
down_threshold value.  As a result, down_threshold lower than 11 is not
allowed even though values from 1 to 10 do work correctly too. The
comment ("cannot be lower than 11 otherwise freq will not fall") also
does not apply after removing the substraction.

For this reason, allow down_threshold to take any value from 1 to 99
and fix the related comment.

Fixes: 27ed3cd2ebf4 (cpufreq: conservative: Fix the logic in frequency decrease checking)
Signed-off-by: Tomasz Wilczyński <twilczynski@naver.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/cpufreq/cpufreq_conservative.c