power_domain.txt 2.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778
  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. Optional properties:
  18. - power-domains : A phandle and PM domain specifier as defined by bindings of
  19. the power controller specified by phandle.
  20. Some power domains might be powered from another power domain (or have
  21. other hardware specific dependencies). For representing such dependency
  22. a standard PM domain consumer binding is used. When provided, all domains
  23. created by the given provider should be subdomains of the domain
  24. specified by this binding. More details about power domain specifier are
  25. available in the next section.
  26. Example:
  27. power: power-controller@12340000 {
  28. compatible = "foo,power-controller";
  29. reg = <0x12340000 0x1000>;
  30. #power-domain-cells = <1>;
  31. };
  32. The node above defines a power controller that is a PM domain provider and
  33. expects one cell as its phandle argument.
  34. Example 2:
  35. parent: power-controller@12340000 {
  36. compatible = "foo,power-controller";
  37. reg = <0x12340000 0x1000>;
  38. #power-domain-cells = <1>;
  39. };
  40. child: power-controller@12341000 {
  41. compatible = "foo,power-controller";
  42. reg = <0x12341000 0x1000>;
  43. power-domains = <&parent 0>;
  44. #power-domain-cells = <1>;
  45. };
  46. The nodes above define two power controllers: 'parent' and 'child'.
  47. Domains created by the 'child' power controller are subdomains of '0' power
  48. domain provided by the 'parent' power controller.
  49. ==PM domain consumers==
  50. Required properties:
  51. - power-domains : A phandle and PM domain specifier as defined by bindings of
  52. the power controller specified by phandle.
  53. Example:
  54. leaky-device@12350000 {
  55. compatible = "foo,i-leak-current";
  56. reg = <0x12350000 0x1000>;
  57. power-domains = <&power 0>;
  58. };
  59. The node above defines a typical PM domain consumer device, which is located
  60. inside a PM domain with index 0 of a power controller represented by a node
  61. with the label "power".