blob: 0e190e20fed8ca0994c90cce2fe631729ce67dec [file] [log] [blame]
Andreas Dannenberg24c6e912018-08-27 15:57:45 +05301Texas Instruments TI SCI Generic Power Domain
2=============================================
3
4Some TI SoCs contain a system controller (like the SYSFW, etc...) that is
5responsible for controlling the state of the IPs that are present.
6Communication between the host processor running an OS and the system
7controller happens through a protocol known as TI SCI [1].
8
9[1] http://processors.wiki.ti.com/index.php/TISCI
10
11PM Domain Node
12==============
13The PM domain node represents the global PM domain managed by the SYSFW. Because
14this relies on the TI SCI protocol to communicate with the SYSFW it must be a
15child of the sysfw node.
16
17Required Properties:
18--------------------
19- compatible: Must be "ti,sci-pm-domain"
20- #power-domain-cells: Must be 1 so that an id can be provided in each
21 device node.
22
23Example (AM65x):
24----------------
25 sysfw: sysfw {
26 compatible = "ti,am654-system-controller";
27 ...
28 k3_pds: power-controller {
29 compatible = "ti,sci-pm-domain";
30 #power-domain-cells = <1>;
31 };
32 };
33
34PM Domain Consumers
35===================
36Hardware blocks belonging to a PM domain should contain a "power-domains"
37property that is a phandle pointing to the corresponding PM domain node
38along with an index representing the device id to be passed to the PMMC
39for device control.
40
41Required Properties:
42--------------------
43- power-domains: phandle pointing to the corresponding PM domain node
44 and an ID representing the device.
45
46Example (AM65x):
47----------------
48 uart2: serial@02800000 {
49 compatible = "ti,omap4-uart";
50 ...
51 power-domains = <&k3_pds 0x3f>;
52 };