On 03/10/13 10:00, Viresh Kumar wrote: > On 3 October 2013 14:27, Sudeep KarkadaNagesha > <Sudeep.KarkadaNagesha@xxxxxxx> wrote: >> Agreed, but there's no cluster node in DT. So platforms using DT would have >> these clocks in cpu@n node as it's used for CPU frequency scaling. One example I >> can see is highbank(it uses cpufreq-cpu0 meaning its single cluster clock). So >> AFAICT if any big-little systems wants to pass cluster clocks through DT, it has >> to be cpu@n nodes. Let me know if you have any alternate thoughts ? > > I understand your point, but shouldn't we name it then: cpu clock? > Probably cluster clock was wrong from the beginning.. As there is no cluster clock, > or there is ? :) > 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 ? Regards, Sudeep -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
