[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohponitwHj40xx_TWjhgVxdqOZ5_dpOB_3avTs=+vo4Ng-gA@mail.gmail.com>
Date: Wed, 9 Jul 2014 20:50:53 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Santosh Shilimkar <santosh.shilimkar@...com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Shawn Guo <shawn.guo@...aro.org>, Nishanth Menon <nm@...com>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
Tomasz Figa <t.figa@...sung.com>,
Stephen Boyd <sboyd@...eaurora.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thomas P Abraham <thomas.ab@...sung.com>,
Arvind Chauhan <arvind.chauhan@....com>,
Sachin Kamat <spk.linux@...il.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>
Subject: Re: [PATCH 02/14] clk: Create of_clk_shared_by_cpus()
On 9 July 2014 20:08, Santosh Shilimkar <santosh.shilimkar@...com> 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists