[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d1cccb6b-e938-6522-c45f-5b613567cb4e@arm.com>
Date: Mon, 9 Jan 2017 09:58:37 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Michał Zegan <webczat_200@...zta.onet.pl>
Cc: linux-clk@...r.kernel.org, Stephen Boyd <sboyd@...eaurora.org>,
Michael Turquette <mturquette@...libre.com>,
Sudeep Holla <sudeep.holla@....com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Neil Armstrong <narmstrong@...libre.com>
Subject: Re: [PATCH] clk: scpi: don't add cpufreq device if the scpi dvfs node
is disabled
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@...zta.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@...zta.onet.pl>
>> Cc: Neil Armstrong <narmstrong@...libre.com>
>> Cc: Michael Turquette <mturquette@...libre.com>
>> Cc: Stephen Boyd <sboyd@...eaurora.org>
>> Signed-off-by: Sudeep Holla <sudeep.holla@....com>
--
Regards,
Sudeep
Powered by blists - more mailing lists