27 Jun
2014
27 Jun
'14
2:15 a.m.
On 27 June 2014 07:23, Mike Turquette mturquette@linaro.org wrote:
but it isn't future-proof if/when the clock framework starts returning dynamically allocated clock pointers for each clk_get() invocation. Maybe we need a function in the common clock framework that tells us if the clocks are the same either via DT or by taking two clock pointers?
I looked through the patch briefly and did not see why we would need to do this. Any hint?
We want to know which CPUs are sharing clock line, so that we can fill affected-cpus field of cpufreq core.