From: Namhyung Kim <namhyung@kernel.org> Date: 2013-02-28 05:38:29
From: Namhyung Kim <redacted>
If we're on the lowest frequency, no need to calculate new freq.
Break out even earlier in this case.
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
---
drivers/cpufreq/cpufreq_conservative.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
From: Namhyung Kim <namhyung@kernel.org> Date: 2013-02-28 05:38:32
From: Namhyung Kim <redacted>
The relation should be CPUFREQ_RELATION_L to find optimal frequency
when decreasing.
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
---
drivers/cpufreq/cpufreq_conservative.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On 28 February 2013 11:08, Namhyung Kim [off-list ref] wrote:
quoted hunk
From: Namhyung Kim <redacted>
The relation should be CPUFREQ_RELATION_L to find optimal frequency
when decreasing.
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
---
drivers/cpufreq/cpufreq_conservative.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Other two patches are fine but really not sure about this one.
When decreasing freq, what do we want:
- lowest frequency at or above target, i.e. >= requested_freq
- highest frequency below or at target, i.e. <= requested_freq
I thought second option was better and so CPUFREQ_RELATION_H
suits more. What made you do this change?