On Tue, Mar 03, 2015 at 06:40:23PM +0530, Viresh Kumar wrote: > On 3 March 2015 at 18:33, Leo Yan <leo....@linaro.org> wrote: > > In the previous code, cpufreq-dt driver support single clock shared by > > all CPUs or every CPU has dedicated clock; but it cannot support cluster > > level clock domain, which is very common implementation for ARM SoCs. > > > > So this patch add the support for cluster level clock; which use the > > platform parameter "clk_domain_boundary" to indicate whether the clock > > domain is bound to system level, cluster level or CPU level. > > > > Signed-off-by: Leo Yan <leo....@linaro.org> > > No. We aren't going to do it this way. You just test your current SoC where > all CPUs share clock line. The other SoC that might come later, where > clocks are per cluster, can be handled later. > > So, for now you don't need any changes in the driver I believe.
Correct, current SoC shares one clock line. I'm just thinking to finish things in one time. From my previous experience, clocks per cluster are common cases for ARM's multi-clusters, so i think it's reasonable to add related support. Regarding of testing this patch, i created two virtual clocks for every cluster and passed the test. Do u think this is acceptable? Thanks, Leo Yan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
