OSDN Git Service

ARM: vexpress: Set-up shared OPP table instead of individual for each CPU
authorSudeep Holla <sudeep.holla@arm.com>
Wed, 27 Nov 2019 15:56:40 +0000 (15:56 +0000)
committerSudeep Holla <sudeep.holla@arm.com>
Mon, 9 Dec 2019 11:52:50 +0000 (11:52 +0000)
commit2a76352ad2cc6b78e58f737714879cc860903802
treea5997465866fae905ab0f77504cbdf13ca5e5ba0
parente42617b825f8073569da76dc4510bfa019b1c35a
ARM: vexpress: Set-up shared OPP table instead of individual for each CPU

Currently we add individual copy of same OPP table for each CPU within
the cluster. This is redundant and doesn't reflect the reality.

We can't use core cpumask to set policy->cpus in ve_spc_cpufreq_init()
anymore as it gets called via cpuhp_cpufreq_online()->cpufreq_online()
->cpufreq_driver->init() and the cpumask gets updated upon CPU hotplug
operations. It also may cause issues when the vexpress_spc_cpufreq
driver is built as a module.

Since ve_spc_clk_init is built-in device initcall, we should be able to
use the same topology_core_cpumask to set the opp sharing cpumask via
dev_pm_opp_set_sharing_cpus and use the same later in the driver via
dev_pm_opp_get_sharing_cpus.

Cc: Liviu Dudau <liviu.dudau@arm.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Tested-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
arch/arm/mach-vexpress/spc.c