summaryrefslogtreecommitdiff
path: root/arch/arm/mach-ixp4xx/Kconfig
diff options
context:
space:
mode:
authorStephen Boyd <swboyd@chromium.org>2019-03-20 15:19:08 +0530
committerViresh Kumar <viresh.kumar@linaro.org>2019-06-17 09:47:32 +0530
commitb3e3759ee4abd72bedbf4b109ff1749d3aea6f21 (patch)
tree1fdb241064ffe49fc2374369815154c87dae5896 /arch/arm/mach-ixp4xx/Kconfig
parentc0ab9e0812da8e2134dd63d030c8a8abd2112a5a (diff)
opp: Don't overwrite rounded clk rate
The OPP table normally contains 'fmax' values corresponding to the voltage or performance levels of each OPP, but we don't necessarily want all the devices to run at fmax all the time. Running at fmax makes sense for devices like CPU/GPU, which have a finite amount of work to do and since a specific amount of energy is consumed at an OPP, its better to run at the highest possible frequency for that voltage value. On the other hand, we have IO devices which need to run at specific frequencies only for their proper functioning, instead of maximum possible frequency. The OPP core currently roundup to the next possible OPP for a frequency and select the fmax value. To support the IO devices by the OPP core, lets do the roundup to fetch the voltage or performance state values, but not use the OPP frequency value. Rather use the value returned by clk_round_rate(). The current user, cpufreq, of dev_pm_opp_set_rate() already does the rounding to the next OPP before calling this routine and it won't have any side affects because of this change. Signed-off-by: Stephen Boyd <swboyd@chromium.org> Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org> [ Viresh: Massaged changelog, added comment and use temp_opp variable instead ] Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Diffstat (limited to 'arch/arm/mach-ixp4xx/Kconfig')
0 files changed, 0 insertions, 0 deletions