Add optional generic PM QoS device latency properties to the bindings and example.
Signed-off-by: Geert Uytterhoeven <[email protected]> --- v6: - Rebased on top of v4.1-rc1 for new RFC, v4: - New. --- Documentation/devicetree/bindings/power/renesas,sysc-rmobile.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/power/renesas,sysc-rmobile.txt b/Documentation/devicetree/bindings/power/renesas,sysc-rmobile.txt index 0a6f03a136792e84..e54ee193c9f8e263 100644 --- a/Documentation/devicetree/bindings/power/renesas,sysc-rmobile.txt +++ b/Documentation/devicetree/bindings/power/renesas,sysc-rmobile.txt @@ -95,7 +95,8 @@ which is a subdomain of A4S. == PM Domain Consumers == Hardware blocks belonging to a PM domain should contain a "power-domains" -property that is a phandle pointing to the corresponding PM domain node. +property that is a phandle pointing to the corresponding PM domain node, +and optional PM QoS device latencies: Example: @@ -104,5 +105,7 @@ Example: reg = <0xe6600000 0x100>; clocks = <&mstp3_clks R8A7740_CLK_TPU0>; power-domains = <&pd_a3sp>; + stop-latency = <250000>; + start-latency = <250000>; #pwm-cells = <3>; }; -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
