power_domain.txt 1.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  1. * Generic PM domains
  2. System on chip designs are often divided into multiple PM domains that can be
  3. used for power gating of selected IP blocks for power saving by reduced leakage
  4. current.
  5. This device tree binding can be used to bind PM domain consumer devices with
  6. their PM domains provided by PM domain providers. A PM domain provider can be
  7. represented by any node in the device tree and can provide one or more PM
  8. domains. A consumer node can refer to the provider by a phandle and a set of
  9. phandle arguments (so called PM domain specifiers) of length specified by the
  10. #power-domain-cells property in the PM domain provider node.
  11. ==PM domain providers==
  12. Required properties:
  13. - #power-domain-cells : Number of cells in a PM domain specifier;
  14. Typically 0 for nodes representing a single PM domain and 1 for nodes
  15. providing multiple PM domains (e.g. power controllers), but can be any value
  16. as specified by device tree binding documentation of particular provider.
  17. Example:
  18. power: power-controller@12340000 {
  19. compatible = "foo,power-controller";
  20. reg = <0x12340000 0x1000>;
  21. #power-domain-cells = <1>;
  22. };
  23. The node above defines a power controller that is a PM domain provider and
  24. expects one cell as its phandle argument.
  25. ==PM domain consumers==
  26. Required properties:
  27. - power-domains : A phandle and PM domain specifier as defined by bindings of
  28. the power controller specified by phandle.
  29. Example:
  30. leaky-device@12350000 {
  31. compatible = "foo,i-leak-current";
  32. reg = <0x12350000 0x1000>;
  33. power-domains = <&power 0>;
  34. };
  35. The node above defines a typical PM domain consumer device, which is located
  36. inside a PM domain with index 0 of a power controller represented by a node
  37. with the label "power".