Re: [PATCH v3 1/7 RESEND] PM / Domains: Add a note about power domain subdomains

2015-01-14 Thread Geert Uytterhoeven
On Wed, Jan 14, 2015 at 3:12 PM, Marek Szyprowski
m.szyprow...@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.

 Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com

Acked-by: Geert Uytterhoeven geert+rene...@glider.be

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@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 majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v3 1/7 RESEND] PM / Domains: Add a note about power domain subdomains

2015-01-14 Thread Ulf Hansson
On 14 January 2015 at 15:12, Marek Szyprowski m.szyprow...@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.

 Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com

Reviewed-by: Ulf Hansson ulf.hans...@linaro.org

Kind regards
Uffe

 ---
 RESEND version:
 - fixed spelling mistakes, thanks go to Geert!
 ---
  .../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 another power domain (or have
 +   other hardware specific dependencies). For representing such dependency
 +   a standard PM domain consumer binding is used. When provided, all domains
 +   created by the given provider should be subdomains of the domain
 +   specified by this binding. More details about power domain specifier are
 +   available in the next section.
 +
  Example:

 power: power-controller@1234 {
 @@ -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@1234 {
 +   compatible = foo,power-controller;
 +   reg = 0x1234 0x1000;
 +   #power-domain-cells = 1;
 +   };
 +
 +   child: power-controller@1234 {
 +   compatible = foo,power-controller;
 +   reg = 0x12341000 0x1000;
 +   power-domains = parent 0;
 +   #power-domain-cells = 1;
 +   };
 +
 +The nodes above define two power controllers: 'parent' and 'child'.
 +Domains created by the 'child' power controller are subdomains of '0' power
 +domain provided by the 'parent' power controller.
 +
  ==PM domain consumers==

  Required properties:
 --
 1.9.2

--
To unsubscribe from this list: send the line unsubscribe devicetree in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[PATCH v3 1/7 RESEND] PM / Domains: Add a note about power domain subdomains

2015-01-14 Thread Marek Szyprowski
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.szyprow...@samsung.com
---
RESEND version:
- fixed spelling mistakes, thanks go to Geert!
---
 .../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 another power domain (or have
+   other hardware specific dependencies). For representing such dependency
+   a standard PM domain consumer binding is used. When provided, all domains
+   created by the given provider should be subdomains of the domain
+   specified by this binding. More details about power domain specifier are
+   available in the next section.
+
 Example:
 
power: power-controller@1234 {
@@ -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@1234 {
+   compatible = foo,power-controller;
+   reg = 0x1234 0x1000;
+   #power-domain-cells = 1;
+   };
+
+   child: power-controller@1234 {
+   compatible = foo,power-controller;
+   reg = 0x12341000 0x1000;
+   power-domains = parent 0;
+   #power-domain-cells = 1;
+   };
+
+The nodes above define two power controllers: 'parent' and 'child'.
+Domains created by the 'child' power controller are subdomains of '0' power
+domain provided by the 'parent' power controller.
+
 ==PM domain consumers==
 
 Required properties:
-- 
1.9.2

--
To unsubscribe from this list: send the line unsubscribe devicetree in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html