OPP: Don't try to remove all OPP tables on failure
authorViresh Kumar <viresh.kumar@linaro.org>
Thu, 13 Sep 2018 07:39:27 +0000 (13:09 +0530)
committerViresh Kumar <viresh.kumar@linaro.org>
Wed, 19 Sep 2018 21:56:40 +0000 (14:56 -0700)
commit404b1369ea26f598b96ae4d3183262a879703cfe
treedf57c469958d52b0a6f1b45da07c16443f812492
parent2fbb8670b4ff4454f1c0de510f788d737edc4b90
OPP: Don't try to remove all OPP tables on failure

dev_pm_opp_of_cpumask_add_table() creates the OPP table for all CPUs
present in the cpumask and on errors it should revert all changes it has
done.

It actually is doing a bit more than that. On errors, it tries to free
all the OPP tables, even the one it hasn't created yet. This may also
end up freeing the OPP tables which were created from separate path,
like dev_pm_opp_set_supported_hw().

Reported-and-tested-by: Niklas Cassel <niklas.cassel@linaro.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
drivers/opp/cpu.c
drivers/opp/of.c
drivers/opp/opp.h