Messages in this thread Patch in this message | | | From | Geert Uytterhoeven <> | Subject | [PATCH/RFC v6 4/7] PM / Domains: Add DT bindings for PM QoS device latencies | Date | Mon, 27 Apr 2015 14:43:39 +0200 |
| |
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, + 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
| |