Message ID | 1410183344-14756-3-git-send-email-geert+renesas@glider.be |
---|---|
State | Superseded, archived |
Headers | show |
Hi Geert, Thanks for your patch. On 9/8/2014 10:35 PM, Geert Uytterhoeven wrote: > A.o., the Renesas R-Mobile System Controller provides power management > support, following the generic PM domain bindings in > Documentation/devicetree/bindings/power/power_domain.txt. > > For now this supports the R-Mobile A1 (r8a7740) only, but it should be > sufficiently generic to handle other members of the SH-Mobile/R-Mobile > family in the future. > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> > --- > .../bindings/power/renesas,sysc-rmobile.txt | 106 +++++++++++++++++++++ > 1 file changed, 106 insertions(+) > create mode 100644 Documentation/devicetree/bindings/power/renesas,sysc-rmobile.txt > > diff --git a/Documentation/devicetree/bindings/power/renesas,sysc-rmobile.txt b/Documentation/devicetree/bindings/power/renesas,sysc-rmobile.txt > new file mode 100644 > index 000000000000..8d9d64df0088 > --- /dev/null > +++ b/Documentation/devicetree/bindings/power/renesas,sysc-rmobile.txt > @@ -0,0 +1,106 @@ > +DT bindings for the Renesas R-Mobile System Controller > + > +== System Controller Node == > + > +The R-Mobile System Controller provides the following functions: > + - Boot mode management, > + - Reset generation, > + - Power management. > + > +Required properties: > +- compatible: Should be "renesas,sysc-<soctype>", "renesas,sysc-rmobile" as > + fallback. > + Examples with soctypes are: > + - "renesas,sysc-r8a7740" (R-Mobile A1) > +- reg: Two address start and address range blocks for the device: > + - The first block refers to the normally accessible registers, > + - the second block refers to the registers protected by the HPB > + semaphore. > + > +Optional nodes: > +- pm-domains: This node contains a hierarchy of PM domain nodes, which should > + match the Power Area Hierarchy in the Power Domain Specifications section of > + the device's datasheet. > + > + > +== PM Domain Nodes == > + > +Each of the PM domain nodes represents a PM domain, as documented by the > +generic PM domain bindings in > +Documentation/devicetree/bindings/power/power_domain.txt. > + > +The nodes should be named by the real power area names, and thus their names > +should be unique. > + > +Required properties: > + - #power-domain-cells: Must be 0. > + > +Optional properties: > +- reg: If the PM domain is not always-on, this property must contain the bit > + index number for the corresponding power area in the various Power > + Control and Status Registers. The parent's node must contain the > + following two properties: > + - #address-cells: Must be 1, > + - #address-cells: Must be 0. Should it be "#size-cells: Must be 0." ? > + If the PM domain is always-on, this property must be omitted. > +- power-on-latency: Power-on latency of the PM domain, in ns, > +- power-off-latency: Power-off latency of the PM domain, in ns. > + > + > +Example: > + > +This shows a subset of the r8a7740 PM domain hierarchy, containing the > +C5 "always-on" domain, 2 of its subdomains (A4S and A4SU), and the A3SP domain, > +which is a subdomain of A4S. > + > + sysc: system-controller@e6180000 { > + compatible = "renesas,sysc-r8a7740", "renesas,sysc-rmobile"; > + reg = <0xe6180000 8000>, <0xe6188000 8000>; > + > + pm-domains { > + pd_c5: c5 { > + #address-cells = <1>; > + #size-cells = <0>; > + #power-domain-cells = <0>; > + > + pd_a4s: a4s@10 { > + reg = <10>; > + #address-cells = <1>; > + #size-cells = <0>; > + #power-domain-cells = <0>; > + power-on-latency = <250000>; > + power-off-latency = <250000>; > + > + pd_a3sp: a3sp@11 { > + reg = <11>; > + #power-domain-cells = <0>; > + power-on-latency = <250000>; > + power-off-latency = <250000>; > + }; > + }; > + > + pd_a4su: a4su@20 { > + reg = <20>; > + #power-domain-cells = <0>; > + power-on-latency = <250000>; > + power-off-latency = <250000>; > + }; > + }; > + }; > + }; > + > + > +== 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. > + > +Example: > + > + tpu: pwm@e6600000 { > + compatible = "renesas,tpu-r8a7740", "renesas,tpu"; > + reg = <0xe6600000 0x100>; > + clocks = <&mstp3_clks R8A7740_CLK_TPU0>; > + power-domains = <&pd_a3sp>; > + #pwm-cells = <3>; > + }; >
Hi Khiem-san, On Tue, Sep 9, 2014 at 12:44 AM, Khiem Nguyen <khiem.nguyen.xt@renesas.com> wrote: >> + - #address-cells: Must be 1, >> + - #address-cells: Must be 0. > > Should it be "#size-cells: Must be 0." ? Yes, obviously. Thanks, will fix. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- 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/renesas,sysc-rmobile.txt b/Documentation/devicetree/bindings/power/renesas,sysc-rmobile.txt new file mode 100644 index 000000000000..8d9d64df0088 --- /dev/null +++ b/Documentation/devicetree/bindings/power/renesas,sysc-rmobile.txt @@ -0,0 +1,106 @@ +DT bindings for the Renesas R-Mobile System Controller + +== System Controller Node == + +The R-Mobile System Controller provides the following functions: + - Boot mode management, + - Reset generation, + - Power management. + +Required properties: +- compatible: Should be "renesas,sysc-<soctype>", "renesas,sysc-rmobile" as + fallback. + Examples with soctypes are: + - "renesas,sysc-r8a7740" (R-Mobile A1) +- reg: Two address start and address range blocks for the device: + - The first block refers to the normally accessible registers, + - the second block refers to the registers protected by the HPB + semaphore. + +Optional nodes: +- pm-domains: This node contains a hierarchy of PM domain nodes, which should + match the Power Area Hierarchy in the Power Domain Specifications section of + the device's datasheet. + + +== PM Domain Nodes == + +Each of the PM domain nodes represents a PM domain, as documented by the +generic PM domain bindings in +Documentation/devicetree/bindings/power/power_domain.txt. + +The nodes should be named by the real power area names, and thus their names +should be unique. + +Required properties: + - #power-domain-cells: Must be 0. + +Optional properties: +- reg: If the PM domain is not always-on, this property must contain the bit + index number for the corresponding power area in the various Power + Control and Status Registers. The parent's node must contain the + following two properties: + - #address-cells: Must be 1, + - #address-cells: Must be 0. + If the PM domain is always-on, this property must be omitted. +- power-on-latency: Power-on latency of the PM domain, in ns, +- power-off-latency: Power-off latency of the PM domain, in ns. + + +Example: + +This shows a subset of the r8a7740 PM domain hierarchy, containing the +C5 "always-on" domain, 2 of its subdomains (A4S and A4SU), and the A3SP domain, +which is a subdomain of A4S. + + sysc: system-controller@e6180000 { + compatible = "renesas,sysc-r8a7740", "renesas,sysc-rmobile"; + reg = <0xe6180000 8000>, <0xe6188000 8000>; + + pm-domains { + pd_c5: c5 { + #address-cells = <1>; + #size-cells = <0>; + #power-domain-cells = <0>; + + pd_a4s: a4s@10 { + reg = <10>; + #address-cells = <1>; + #size-cells = <0>; + #power-domain-cells = <0>; + power-on-latency = <250000>; + power-off-latency = <250000>; + + pd_a3sp: a3sp@11 { + reg = <11>; + #power-domain-cells = <0>; + power-on-latency = <250000>; + power-off-latency = <250000>; + }; + }; + + pd_a4su: a4su@20 { + reg = <20>; + #power-domain-cells = <0>; + power-on-latency = <250000>; + power-off-latency = <250000>; + }; + }; + }; + }; + + +== 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. + +Example: + + tpu: pwm@e6600000 { + compatible = "renesas,tpu-r8a7740", "renesas,tpu"; + reg = <0xe6600000 0x100>; + clocks = <&mstp3_clks R8A7740_CLK_TPU0>; + power-domains = <&pd_a3sp>; + #pwm-cells = <3>; + };
A.o., the Renesas R-Mobile System Controller provides power management support, following the generic PM domain bindings in Documentation/devicetree/bindings/power/power_domain.txt. For now this supports the R-Mobile A1 (r8a7740) only, but it should be sufficiently generic to handle other members of the SH-Mobile/R-Mobile family in the future. Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> --- .../bindings/power/renesas,sysc-rmobile.txt | 106 +++++++++++++++++++++ 1 file changed, 106 insertions(+) create mode 100644 Documentation/devicetree/bindings/power/renesas,sysc-rmobile.txt