On 09/09, Rob Herring wrote: > On 09/09/2015 11:36 AM, Lee Jones wrote: > >>> Or have I got the wrong end of the stick? > >>> > >>> NB: Note the suggested new property names. > >> > >> Yeah, all looks fine to me. > > > > I think these names are better: > > > > opp-supply-range-name => opp-microvolt-names > > opp-cuts => opp-supported-hw > > > > Apart from that, the binding is starting to come together. > > > > Let's see what Rob and Stephen have to say about it. > > Seems reasonable to me. I think it will work for qcom use cases. We can collapse the tables down to one node and have speed bin and version as the opp-supported-hw property. The opp-microvolt-names property would be where we put the different voltage bins. What about the other properties like opp-microamp or opp-suspend? Will all of those also get *-names properties to index into them based on some string? I don't actually need those for my devices, but I'm just pointing it out in case someone else wants to compress tables but they have different microamps or clock latencies, etc. Finally, does this mean we will get rid of operating-points-names? -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- 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
