Viresh Kumar <viresh.kumar@xxxxxxxxxx> writes: > Current OPP (Operating performance point) DT bindings are proven to be > insufficient at multiple instances. > > There had been multiple band-aid approaches to get them fixed (The latest one > being: http://www.mail-archive.com/devicetree@xxxxxxxxxxxxxxx/msg53398.html). > For obvious reasons Rob rejected them and shown the right path forward. > > The shortcomings we are trying to solve here: > > - Getting clock sharing information between CPUs. Single shared clock vs > independent clock per core vs shared clock per cluster. > > - Support for turbo modes > > - Support for intermediate frequencies or OPPs we can switch to. > > - Other per OPP settings: transition latencies, disabled status, etc.? > > - Expandability of OPPs in future. > > This patch introduces new bindings "operating-points-v2" to get these problems > solved. Refer to the bindings for more details. > > Signed-off-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx> [...] > +* OPP Descriptor Node > + > +This describes the OPPs belonging to a device. This node can have following > +properties: > + > +Required properties: > +- compatible: Allow OPPs to express their compatibility. It should be: > + "operating-points-v2". > +- OPP nodes: One or more OPP nodes describing frequency-voltage pairs. Their > + name isn't significant but their phandles can be used to reference an OPP. > + > +Optional properties: > +- shared-opp: Indicates that device nodes using this OPP descriptor's phandle > + switch their DVFS state together, i.e. they share clock lines. ... or shared voltage rail? > + Missing property means devices have independent clock lines, but they share OPPs. huh? missing 'shared-opp' property means they share OPPs? -ECONFUSED. Maybe I missed some of the discussion of why this property is needed, but I'm left wondering why it's needed explicitly. With the OPPs as part of the CPU nodes, shouldnt' the "shared" nature of the OPP be easily derived from the clock and or regulator (opp-supply) property of the CPU nodes? IOW, if two CPU nodes share a clock and/or a regulator, the framework should know it's "shared". Or, were there other reasons besides clocks/regulators why this property was needed (if so, the documentation doesn't describe them.) Kevin -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
