OSDN Git Service

clk: scpi: don't add cpufreq device if the scpi dvfs node is disabled
authorSudeep Holla <sudeep.holla@arm.com>
Fri, 6 Jan 2017 12:34:30 +0000 (12:34 +0000)
committerStephen Boyd <sboyd@codeaurora.org>
Tue, 10 Jan 2017 00:08:19 +0000 (16:08 -0800)
commit67bcc2c5f1da8c5bb58e72354274ea5c59a3950a
tree6b62be7aa0b3360d8f326a76242ddecf90656c53
parent4263499a6e05c42c47c8e22c23575bc79ab62ddf
clk: scpi: don't add cpufreq device if the scpi dvfs node is disabled

Currently we add the virtual cpufreq device unconditionally even when
the SCPI DVFS clock provider node is disabled. This will cause cpufreq
driver to throw errors when it gets initailised on boot/modprobe and
also when the CPUs are hot-plugged back in.

This patch fixes the issue by adding the virtual cpufreq device only if
the SCPI DVFS clock provider is available and registered.

Fixes: 9490f01e2471 ("clk: scpi: add support for cpufreq virtual device")
Reported-by: Michał Zegan <webczat_200@poczta.onet.pl>
Cc: Neil Armstrong <narmstrong@baylibre.com>
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
Tested-by: Michał Zegan <webczat_200@poczta.onet.pl>
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
drivers/clk/clk-scpi.c