Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756122AbaGIPU4 (ORCPT ); Wed, 9 Jul 2014 11:20:56 -0400 Received: from mail-oa0-f45.google.com ([209.85.219.45]:63310 "EHLO mail-oa0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755960AbaGIPUx (ORCPT ); Wed, 9 Jul 2014 11:20:53 -0400 MIME-Version: 1.0 In-Reply-To: <53BD53EA.8050708@ti.com> References: <5f7164d789e87c62d722b575980c92dfd0504334.1404231535.git.viresh.kumar@linaro.org> <53BD53EA.8050708@ti.com> Date: Wed, 9 Jul 2014 20:50:53 +0530 Message-ID: Subject: Re: [PATCH 02/14] clk: Create of_clk_shared_by_cpus() From: Viresh Kumar To: Santosh Shilimkar Cc: "Rafael J. Wysocki" , Shawn Guo , Nishanth Menon , Lists linaro-kernel , "linux-pm@vger.kernel.org" , "linux-arm-msm@vger.kernel.org" , Tomasz Figa , Stephen Boyd , Linux Kernel Mailing List , Thomas P Abraham , Arvind Chauhan , Sachin Kamat , Lorenzo Pieralisi Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9 July 2014 20:08, Santosh Shilimkar wrote: > I might be wrong but this API seems to bit short cited. We should probably > handle it bit better since there are more cases instead of just checking CPU > tuple. More than two CPUs may share the clock so discovering that in one iteration > is better. I also think this is closely related to CPU topology. > > - CPUs part of 'a cluster' shares same clock. > - Multiple clusters may share same clock > - Every CPU might be clocked from separate PLL. All these configurations are currently supported by this series. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/