summaryrefslogtreecommitdiff
path: root/drivers/cpufreq/cpufreq_powersave.c
diff options
context:
space:
mode:
authorNicola Mazzucato <nicola.mazzucato@arm.com>2021-02-19 01:23:25 +0300
committerSudeep Holla <sudeep.holla@arm.com>2021-03-15 16:24:45 +0300
commit80a064dbd556cde36f0b7f1778e8d8a1dc50f19f (patch)
tree32470d0dbba1877442dba77901638c52794a8eea /drivers/cpufreq/cpufreq_powersave.c
parent71a37cd6a59dc58df3f4e58db3f4f04c9e69da43 (diff)
downloadlinux-80a064dbd556cde36f0b7f1778e8d8a1dc50f19f.tar.xz
scmi-cpufreq: Get opp_shared_cpus from opp-v2 for EM
By design, SCMI performance domains define the granularity of performance controls, they do not describe any underlying hardware dependencies (although they may match in many cases). It is therefore possible to have some platforms where hardware may have the ability to control CPU performance at different granularity and choose to describe fine-grained performance control through SCMI. In such situations, the energy model would be provided with inaccurate information based on controls, while it still needs to know the performance boundaries. To restore correct functionality, retrieve information of CPUs under the same performance domain from operating-points-v2 in DT, and pass it on to EM. Link: https://lore.kernel.org/r/20210218222326.15788-3-nicola.mazzucato@arm.com Acked-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Nicola Mazzucato <nicola.mazzucato@arm.com> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
Diffstat (limited to 'drivers/cpufreq/cpufreq_powersave.c')
0 files changed, 0 insertions, 0 deletions