cpufreq: add support for intermediate (stable) frequencies
authorViresh Kumar <viresh.kumar@linaro.org>
Mon, 2 Jun 2014 17:19:28 +0000 (22:49 +0530)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Thu, 5 Jun 2014 21:32:29 +0000 (23:32 +0200)
commit1c03a2d04d7ab6d27c1fef8614f08187d974bd21
tree3d0ad7be510d75f6b3a9caa91d027e4e31e35300
parent5ece2399181a5abaf42a4cb607463770686778e6
cpufreq: add support for intermediate (stable) frequencies

Douglas Anderson, recently pointed out an interesting problem due to which
udelay() was expiring earlier than it should.

While transitioning between frequencies few platforms may temporarily switch to
a stable frequency, waiting for the main PLL to stabilize.

For example: When we transition between very low frequencies on exynos, like
between 200MHz and 300MHz, we may temporarily switch to a PLL running at 800MHz.
No CPUFREQ notification is sent for that. That means there's a period of time
when we're running at 800MHz but loops_per_jiffy is calibrated at between 200MHz
and 300MHz. And so udelay behaves badly.

To get this fixed in a generic way, introduce another set of callbacks
get_intermediate() and target_intermediate(), only for drivers with
target_index() and CPUFREQ_ASYNC_NOTIFICATION unset.

get_intermediate() should return a stable intermediate frequency platform wants
to switch to, and target_intermediate() should set CPU to that frequency,
before jumping to the frequency corresponding to 'index'. Core will take care of
sending notifications and driver doesn't have to handle them in
target_intermediate() or target_index().

NOTE: ->target_index() should restore to policy->restore_freq in case of
failures as core would send notifications for that.

Tested-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Reviewed-by: Doug Anderson <dianders@chromium.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Documentation/cpu-freq/cpu-drivers.txt
drivers/cpufreq/cpufreq.c
include/linux/cpufreq.h