On 09/11/2015 07:01 AM, Viresh Kumar wrote: > If 'opp-microvolt' is used to specify values for multiple regulators, > then we need this additional information to know if the values passed > should be treated as <target> or <target min max>. Can't you determine this implicitly from # of cells / # of regulators being either 1 or 3? > > This is because, DT doesn't differentiate between these two styles: > > prop = <x>, <y>, <z>; > prop = <x y z>; > > Cc: devicetree@xxxxxxxxxxxxxxx > Signed-off-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx> > --- > Documentation/devicetree/bindings/opp/opp.txt | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > > diff --git a/Documentation/devicetree/bindings/opp/opp.txt b/Documentation/devicetree/bindings/opp/opp.txt > index 8759bc4783ed..719603b87353 100644 > --- a/Documentation/devicetree/bindings/opp/opp.txt > +++ b/Documentation/devicetree/bindings/opp/opp.txt > @@ -76,6 +76,16 @@ This describes the OPPs belonging to a device. This node can have following > present here is important, as that should match the order in which values are > present in 'opp-microvolt' and 'opp-microamp' properties. > > +- opp-microvolt-triplets: This is a required property, only if multiple supplies > + are available for the device. Otherwise it is ignored. > + > + 'opp-microvolt' can be present in two forms: <target> or <target min max>, per > + power-supply. 'opp-microvolt-triplets' property is used to find the form in > + which 'opp-microvolt' is present. > + > + If present, then 'opp-microvolt' must be present in <target min max> form, > + else in <target> form. This implies that bindings currently with triplets are wrong since they will be missing opp-microvolt-triplets. Rob -- 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
