Thread (4 messages) 4 messages, 3 authors, 2015-01-28

[RFC V2] OPP: Redefine bindings to overcome shortcomings

From: viresh.kumar@linaro.org (Viresh Kumar)
Date: 2015-01-23 12:53:03
Also in: linux-devicetree, linux-pm

On 23 January 2015 at 17:09, Lucas Stach [off-list ref] wrote:
Am Freitag, den 23.01.2015, 16:14 +0530 schrieb Viresh Kumar:
quoted
I haven't incorporated the comments given by Mark Brown as I had some doubts.
@broonie: Is this what you wanted to mention earlier ? : http://pastebin.com/1RZTccmm
I think we should work this out for the new bindings, as
voltage-tolerance is a completely bogus value.
Yeah, that's what I was saying. I just wanted to confirm that I understood
it clearly. And so didn't made the changes here.
quoted
+  - opp-microvolt: voltage in micro Volts
Each OPP voltage should be defined by the triplet of minimum,
nominal/typical, maximum. This lets you specify exact tolerances in each
direction and should cover most use-cases.

IMHO it would make sense to just define opp-microvolt as an array of
those 3 values, so the DT doesn't get bloated with a lot more
properties.

A typical value for a CPU could then look like this:
opp-microvolt = <800000 850000 1100000>

For devices without any tolerance you can just specify the same value
three times and be done with it:
opp-microvolt = <900000 900000 900000>
Ok.
quoted
+  Optional properties:
+  - turbo-mode: Marks the volt-freq pair as turbo pair.
+  - status: Marks the node enabled/disabled.
+  - voltage-tolerance: Specify the CPU voltage tolerance in percentage.
Please let's drop this.
Yes, I did dropped it in the pastebin link I gave above.

Thanks again for your feedback.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help