cpufreq: Break out early when frequency equals target_freq
authorStratos Karafotis <stratosk@semaphore.gr>
Wed, 14 May 2014 18:05:52 +0000 (21:05 +0300)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Tue, 20 May 2014 12:02:09 +0000 (14:02 +0200)
commit1e4988563d3c92ba756d8c86917fc1b594ebe855
tree807afe61525fc4fb70f2e84ad6e5ff458f97652d
parente7b453d3dd5f251f13bf4670037af70bf611d0cb
cpufreq: Break out early when frequency equals target_freq

Many drivers keep frequencies in frequency table in ascending
or descending order. When governor tries to change to policy->min
or policy->max respectively then the cpufreq_frequency_table_target
could return on first iteration. This will save some iteration cycles.

So, break out early when a frequency in cpufreq_frequency_table
equals to target one.

Testing this during kernel compilation using ondemand governor
with a frequency table in ascending order, the
cpufreq_frequency_table_target returned early on the first
iteration at about 30% of times called.

Signed-off-by: Stratos Karafotis <stratosk@semaphore.gr>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
drivers/cpufreq/freq_table.c