| Message ID | 1430138622-14029-5-git-send-email-geert+renesas@glider.be |
|---|---|
| State | Needs Review / ACK, archived |
| Headers | show |
| Context | Check | Description |
|---|---|---|
| robh/checkpatch | warning | total: 1 errors, 0 warnings, 0 lines checked |
| robh/patch-applied | success |
On 27 April 2015 at 14:43, Geert Uytterhoeven <geert+renesas@glider.be> wrote: > PM QoS device start/stop are properties of the hardware. > In legacy code, they're specified from platform code. > On DT platforms, their values should come from DT. > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> > --- > v6: > - Rebased on top of v4.1-rc1 for new RFC, > > v4: > - Drop save/restore state latencies, as they're Linux driver-specific, > - Change state to RFC, as this is put on hold, > > v3: > - No changes, > > v2: > - New. > --- > Documentation/devicetree/bindings/power/power_domain.txt | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/power/power_domain.txt b/Documentation/devicetree/bindings/power/power_domain.txt > index d659e5cb39be6057..32d1d3a399fe2a48 100644 > --- a/Documentation/devicetree/bindings/power/power_domain.txt > +++ b/Documentation/devicetree/bindings/power/power_domain.txt > @@ -73,12 +73,18 @@ Required properties: > - power-domains : A phandle and PM domain specifier as defined by bindings of > the power controller specified by phandle. > > +Optional properties: > + - stop-latency: Stop latency of the device, in ns, > + - start-latency: Start latency of the device, in ns, > + What do you think of renaming these to "suspend-latency" and "resume-latency" instead? I think that better reflects their purpose. I have no strong opinion though. > Example: > > leaky-device@12350000 { > compatible = "foo,i-leak-current"; > reg = <0x12350000 0x1000>; > power-domains = <&power 0>; > + stop-latency = <250000>; > + start-latency = <250000>; > }; > > The node above defines a typical PM domain consumer device, which is located > -- > 1.9.1 > Kind regards Uffe -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/power/power_domain.txt b/Documentation/devicetree/bindings/power/power_domain.txt index d659e5cb39be6057..32d1d3a399fe2a48 100644 --- a/Documentation/devicetree/bindings/power/power_domain.txt +++ b/Documentation/devicetree/bindings/power/power_domain.txt @@ -73,12 +73,18 @@ Required properties: - power-domains : A phandle and PM domain specifier as defined by bindings of the power controller specified by phandle. +Optional properties: + - stop-latency: Stop latency of the device, in ns, + - start-latency: Start latency of the device, in ns, + Example: leaky-device@12350000 { compatible = "foo,i-leak-current"; reg = <0x12350000 0x1000>; power-domains = <&power 0>; + stop-latency = <250000>; + start-latency = <250000>; }; The node above defines a typical PM domain consumer device, which is located
PM QoS device start/stop are properties of the hardware. In legacy code, they're specified from platform code. On DT platforms, their values should come from DT. Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> --- v6: - Rebased on top of v4.1-rc1 for new RFC, v4: - Drop save/restore state latencies, as they're Linux driver-specific, - Change state to RFC, as this is put on hold, v3: - No changes, v2: - New. --- Documentation/devicetree/bindings/power/power_domain.txt | 6 ++++++ 1 file changed, 6 insertions(+)