From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sudeep KarkadaNagesha Subject: Re: [PATCH] cpufreq: arm-big-little: use clk_get instead of clk_get_sys Date: Thu, 03 Oct 2013 10:50:49 +0100 Message-ID: <524D3DF9.4080005@arm.com> References: <1380619803-2760-1-git-send-email-Sudeep.KarkadaNagesha@arm.com> <524D3170.7080406@arm.com> <524D377C.90200@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: Sender: cpufreq-owner@vger.kernel.org To: Viresh Kumar Cc: "cpufreq@vger.kernel.org" , "linux-pm@vger.kernel.org" , "Rafael J. Wysocki" , Sudeep KarkadaNagesha List-Id: linux-pm@vger.kernel.org On 03/10/13 10:38, Viresh Kumar wrote: > On 3 October 2013 14:53, Sudeep KarkadaNagesha > wrote: >> Ok I would phrase it as, it's a clock shared by all the cpus in the cluster. >> So like any other shared clocks in the system, each device sharing it would have >> it as input clock but it would be single clock output from the clock/power >> controller. Does it make any sense ? > > Sure.. I already know that :) .. what I am not able to decide is, if we should > talk about CPU clocks in our driver or cluster clocks.. > I understand. Having cpu-cluster. helps platforms not specifying cpu clocks in DT or not registering clocks using cpu_dev. If you enforce clock lookups with dev_id(cpu) then I believe you can remove 'cpu-cluster.', that's your call :) Regards, Sudeep