blob: e7e2d13f9fb4883ebb935a537190dd187e5557a5 [file] [log] [blame]
Andreas Dannenberg4cfdf4d2018-08-27 15:57:41 +05301Texas Instruments TI SCI Reset Controller
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
11Reset Controller Node
12=====================
13The reset controller node represents the resets of various hardware modules
14present on the SoC managed by the SYSFW. Because this relies on the TI SCI
15protocol to communicate with the SYSFW it must be a child of the sysfw node.
16
17Required Properties:
18--------------------
19 - compatible: Must be "ti,sci-reset"
20 - #reset-cells: Must be 2. Please see the reset consumer node below for
21 usage details.
22
23Example (AM65x):
24----------------
25 sysfw: sysfw {
26 compatible = "ti,am654-system-controller";
27 ...
28 k3_reset: reset-controller {
29 compatible = "ti,sci-reset";
30 #reset-cells = <2>;
31 };
32 };
33
34Reset Consumers
35===============
36Each of the reset consumer nodes should have the following properties,
37in addition to their own properties.
38
39Required Properties:
40--------------------
41 - resets: A phandle and reset specifier pair, one pair for each reset signal
42 that affects the device, or that the device manages. The phandle
43 should point to the TI SCI reset controller node, and the reset
44 specifier should have 2 cell-values. The first cell should contain
45 the device ID. The second cell should contain the reset mask value
46 used by system controller.
47
48Example (AM65x):
49----------------
50 uart2: serial@02800000 {
51 compatible = "ti,omap4-uart";
52 ...
53 resets = <&k3_reset 5 1>;
54 };