cpufreq: tegra186: Break after initialization is done for policy->cpu
There are two clusters (2 + 4 CPUs) on this platform and a separate cpufreq policy is available for each of the CPUs. The loop in tegra186_cpufreq_init() tries to find the structure for the right CPU and finish initialization. But it is missing a `break` statement at the end, which forces it to restart the loop even when the CPU already matched and initialization is done. Fix that by adding the missing `break` statement. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> Reviewed-by: Mikko Perttunen <mperttunen@nvidia.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
This commit is contained in:
parent
d417e0691a
commit
3e3b507ef6
|
@ -79,6 +79,7 @@ static int tegra186_cpufreq_init(struct cpufreq_policy *policy)
|
|||
policy->driver_data =
|
||||
data->regs + info->offset + EDVD_CORE_VOLT_FREQ(core);
|
||||
cpufreq_table_validate_and_show(policy, cluster->table);
|
||||
break;
|
||||
}
|
||||
|
||||
policy->cpuinfo.transition_latency = 300 * 1000;
|
||||
|
|
Loading…
Reference in New Issue