cpufreq: tegra186: Break after initialization is done for policy->cpu
authorViresh Kumar <viresh.kumar@linaro.org>
Thu, 22 Feb 2018 09:54:57 +0000 (15:24 +0530)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Tue, 27 Feb 2018 17:22:12 +0000 (18:22 +0100)
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>
drivers/cpufreq/tegra186-cpufreq.c

index fe78753..771df64 100644 (file)
@@ -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;