diff options
author | 2018-02-22 15:24:57 +0530 | |
---|---|---|
committer | 2018-02-27 18:22:12 +0100 | |
commit | 3e3b507ef60cb53c209ef8f5d0fef48ddff1b3f4 (patch) | |
tree | 5c57997a21f147effc6a513d09f92c232c21b2e5 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | cpufreq: Validate frequency table in the core (diff) | |
download | linux-rng-3e3b507ef60cb53c209ef8f5d0fef48ddff1b3f4.tar.xz linux-rng-3e3b507ef60cb53c209ef8f5d0fef48ddff1b3f4.zip |
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>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions