On 30/07/13 19:34, Stephen Warren wrote: > On 07/30/2013 12:00 PM, Sudeep KarkadaNagesha wrote: >> From: Sudeep KarkadaNagesha <sudeep.karkadanagesha@xxxxxxx> >> >> If more than one similar devices share the same OPPs, currently we >> need to replicate the OPP entries in all the nodes. >> >> Few drivers like cpufreq depend on physical cpu0 node to specify the >> OPPs and only that node is referred irrespective of the logical cpu >> accessing it. Alternatively to support cpuhotplug path, few drivers >> parse all the cpu nodes for OPPs. Instead we can specify the phandle >> of the node with which the current node shares the operating points. >> >> This patch adds support to specify the phandle in the operating points >> of any device node, where the node specified by the phandle holds the >> actual OPPs. > >> diff --git a/Documentation/devicetree/bindings/power/opp.txt b/Documentation/devicetree/bindings/power/opp.txt > >> +Optional properties: >> +- operating-points-phandle: phandle to the device node with which this > > That's a funny name. Bikeshedding a bit, how about shared-operating-points? shared-operating-points makes sense, but I was thinking that name should indicate it's reference to the device that it shares OPP with. I agree 'operating-points-phandle' is no good, is 'shared-opp-device' any better ? 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
