| Message ID | 1421243091-10778-2-git-send-email-m.szyprowski@samsung.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
Hi Marek, On Wed, Jan 14, 2015 at 2:44 PM, Marek Szyprowski <m.szyprowski@samsung.com> wrote: > This patch adds a note on defining subdomains to generic PM domain > binding documentation to let power domain providers use common approach > for defining power domain hierarchy. Thanks! > Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> > --- > .../devicetree/bindings/power/power_domain.txt | 29 ++++++++++++++++++++++ > 1 file changed, 29 insertions(+) > > diff --git a/Documentation/devicetree/bindings/power/power_domain.txt b/Documentation/devicetree/bindings/power/power_domain.txt > index 98c1667..eeea45b 100644 > --- a/Documentation/devicetree/bindings/power/power_domain.txt > +++ b/Documentation/devicetree/bindings/power/power_domain.txt > @@ -19,6 +19,16 @@ Required properties: > providing multiple PM domains (e.g. power controllers), but can be any value > as specified by device tree binding documentation of particular provider. > > +Optional properties: > + - power-domains : A phandle and PM domain specifier as defined by bindings of > + the power controller specified by phandle. > + Some power domains might be powered from other power domain (or have s/other/another/ > + other hardware specific dependency). For representing such dependency s/dependency/dependencies/ (twice) > + a standard PM domain consumer binging is used. When provided, all domains binding > + created by the given provider should be a subdomain of the domain s/a subdomain/subdomains/ > + specified by this binding. More details about power domain specifier is s/is/are/ > + available in the the next section. duplicate "the" > + > Example: > > power: power-controller@12340000 { > @@ -30,6 +40,25 @@ Example: > The node above defines a power controller that is a PM domain provider and > expects one cell as its phandle argument. > > +Example 2: > + > + parent: power-controller@12340000 { > + compatible = "foo,power-controller"; > + reg = <0x12340000 0x1000>; > + #power-domain-cells = <1>; > + }; > + > + child: power-controller@12340000 { > + compatible = "foo,power-controller"; > + reg = <0x12341000 0x1000>; > + power-domains = <&parent 0>; > + #power-domain-cells = <1>; > + }; > + > +The nodes above defines two power controllers: 'parent' and 'child'. s/defines/define/ > +Domains created by 'child' power controller are subdomains of '0' power the 'child' power controller > +domain provided by 'parent' power controller. the 'parent' power controller. 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 linux-samsung-soc" 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 98c1667..eeea45b 100644 --- a/Documentation/devicetree/bindings/power/power_domain.txt +++ b/Documentation/devicetree/bindings/power/power_domain.txt @@ -19,6 +19,16 @@ Required properties: providing multiple PM domains (e.g. power controllers), but can be any value as specified by device tree binding documentation of particular provider. +Optional properties: + - power-domains : A phandle and PM domain specifier as defined by bindings of + the power controller specified by phandle. + Some power domains might be powered from other power domain (or have + other hardware specific dependency). For representing such dependency + a standard PM domain consumer binging is used. When provided, all domains + created by the given provider should be a subdomain of the domain + specified by this binding. More details about power domain specifier is + available in the the next section. + Example: power: power-controller@12340000 { @@ -30,6 +40,25 @@ Example: The node above defines a power controller that is a PM domain provider and expects one cell as its phandle argument. +Example 2: + + parent: power-controller@12340000 { + compatible = "foo,power-controller"; + reg = <0x12340000 0x1000>; + #power-domain-cells = <1>; + }; + + child: power-controller@12340000 { + compatible = "foo,power-controller"; + reg = <0x12341000 0x1000>; + power-domains = <&parent 0>; + #power-domain-cells = <1>; + }; + +The nodes above defines two power controllers: 'parent' and 'child'. +Domains created by 'child' power controller are subdomains of '0' power +domain provided by 'parent' power controller. + ==PM domain consumers== Required properties:
This patch adds a note on defining subdomains to generic PM domain binding documentation to let power domain providers use common approach for defining power domain hierarchy. Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> --- .../devicetree/bindings/power/power_domain.txt | 29 ++++++++++++++++++++++ 1 file changed, 29 insertions(+)