On 03/10/13 10:38, Viresh Kumar wrote: > On 3 October 2013 14:53, Sudeep KarkadaNagesha > <Sudeep.KarkadaNagesha@xxxxxxx> 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.<n> helps platforms not specifying cpu clocks in DT or not registering clocks using cpu_dev. If you enforce clock lookups with dev_id(cpu<n>) then I believe you can remove 'cpu-cluster.<n>', that's your call :) 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
