diff options
author | Viresh Kumar <viresh.kumar@linaro.org> | 2018-09-07 09:01:54 +0530 |
---|---|---|
committer | Viresh Kumar <viresh.kumar@linaro.org> | 2018-10-01 15:00:31 +0530 |
commit | 283d55e68d8a0f302057f57dcbd4d2e000c2ac85 (patch) | |
tree | bb1114ed98b8416d6926f8f6a82c1017899896f4 /mm/vmpressure.c | |
parent | cdd6ed90cdb6c2fd982909501f0a109274147fb4 (diff) | |
download | linux-283d55e68d8a0f302057f57dcbd4d2e000c2ac85.tar.gz linux-283d55e68d8a0f302057f57dcbd4d2e000c2ac85.tar.bz2 linux-283d55e68d8a0f302057f57dcbd4d2e000c2ac85.zip |
OPP: Prevent creating multiple OPP tables for devices sharing OPP nodes
When two or more devices are sharing their clock and voltage rails, they
share the same OPP table. But there are some corner cases where the OPP
core incorrectly creates separate OPP tables for them.
For example, CPU 0 and 1 share clock/voltage rails. The platform
specific code calls dev_pm_opp_set_regulators() for CPU0 and the OPP
core creates an OPP table for it (the individual OPPs aren't initialized
as of now). The same is repeated for CPU1 then. Because
_opp_get_opp_table() doesn't compare DT node pointers currently, it
fails to find the link between CPU0 and CPU1 and so creates a new OPP
table.
Fix this by calling _managed_opp() from _opp_get_opp_table().
_managed_opp() gain an additional argument (index) to get the right node
pointer. This resulted in simplifying code in _of_add_opp_table_v2() as
well.
Tested-by: Niklas Cassel <niklas.cassel@linaro.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Diffstat (limited to 'mm/vmpressure.c')
0 files changed, 0 insertions, 0 deletions