On Thu, 10 Sep 2015, Viresh Kumar wrote: > On 09-09-15, 17:57, Stephen Boyd wrote: > > I think it will work for qcom use cases. > > Thanks for the Rant Rob, it finally got me moving :) > > > 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 > > I am probably going to remove opp-microvolt-names property as well, if > we are going to use separate entries for all voltage ranges in OPP > node. i.e. two voltage ranges, slow and fast, like this: > > regulator A regulator B > opp-microvolt-slow = <tarA minA maxA>, <tarB minB maxB>; > opp-microvolt-fast = <tarA minA maxA>, <tarB minB maxB>; > > > be where we put the different voltage bins. What about the other > > properties like opp-microamp or opp-suspend? Will all of those > > Lets keep them as is for now, unless we have a real user. > > > 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? > > That's the next thing I wanted to ask from Rob. We are surely not > going to use them and there are no users or kernel code to support > them today. Can we get rid of them from the DT ? I think you answered your own question. No users == !ABI == Strip it out. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- 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
