From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757968AbdAIJ64 (ORCPT ); Mon, 9 Jan 2017 04:58:56 -0500 Received: from foss.arm.com ([217.140.101.70]:49684 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751711AbdAIJ6q (ORCPT ); Mon, 9 Jan 2017 04:58:46 -0500 Subject: Re: [PATCH] clk: scpi: don't add cpufreq device if the scpi dvfs node is disabled To: =?UTF-8?Q?Micha=c5=82_Zegan?= References: <1483706070-12357-1-git-send-email-sudeep.holla@arm.com> Cc: linux-clk@vger.kernel.org, Stephen Boyd , Michael Turquette , Sudeep Holla , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Neil Armstrong From: Sudeep Holla Organization: ARM Message-ID: Date: Mon, 9 Jan 2017 09:58:37 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 ? > 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 >> Cc: Neil Armstrong >> Cc: Michael Turquette >> Cc: Stephen Boyd >> Signed-off-by: Sudeep Holla -- Regards, Sudeep