Round clock frequencies to the nearest possible frequency. Since the OPPs as specified in DT and the CCF use different a resolution for clock frequencies, the clk_round_rate() API may return unexpected results, due to not mandating how rounding has to happen. The clk_find_nearest_rate() API mitigates such issues and finds the appropriate frequency for an OPP. Signed-off-by: Soren Brinkmann <soren.brinkmann@xxxxxxxxxx> --- drivers/cpufreq/cpufreq-cpu0.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/cpufreq/cpufreq-cpu0.c b/drivers/cpufreq/cpufreq-cpu0.c index ee1ae303a07c..1650581f85b6 100644 --- a/drivers/cpufreq/cpufreq-cpu0.c +++ b/drivers/cpufreq/cpufreq-cpu0.c @@ -42,7 +42,8 @@ static int cpu0_set_target(struct cpufreq_policy *policy, unsigned int index) long freq_Hz, freq_exact; int ret; - freq_Hz = clk_round_rate(cpu_clk, freq_table[index].frequency * 1000); + freq_Hz = clk_find_nearest_rate(cpu_clk, + freq_table[index].frequency * 1000); if (freq_Hz <= 0) freq_Hz = freq_table[index].frequency * 1000; -- 2.0.1.1.gfbfc394 -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
