Messages in this thread | | | Subject | Re: [PATCH] clk: scpi: don't add cpufreq device if the scpi dvfs node is disabled | From | Michał Zegan <> | Date | Mon, 9 Jan 2017 11:14:53 +0100 |
| |
Of course.
W dniu 09.01.2017 o 10:58, Sudeep Holla pisze: > > > On 07/01/17 00:44, Michał Zegan wrote: >> seems the patch works as intended. >> > > So, can we take this as > Tested-by: Michał Zegan <webczat_200@poczta.onet.pl> ? > >> W dniu 06.01.2017 o 13:34, Sudeep Holla pisze: >>> 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> >>> Cc: Michael Turquette <mturquette@baylibre.com> >>> Cc: Stephen Boyd <sboyd@codeaurora.org> >>> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> >
[unhandled content-type:application/pgp-signature] | |