Lokesh Vutla | 32cd251 | 2018-08-27 15:57:32 +0530 | [diff] [blame] | 1 | Texas Instruments System Control Interface (TI-SCI) Message Protocol |
| 2 | -------------------------------------------------------------------- |
| 3 | |
| 4 | Texas Instrument's processors including those belonging to Keystone generation |
| 5 | of processors have separate hardware entity which is now responsible for the |
| 6 | management of the System on Chip (SoC) system. These include various system |
| 7 | level functions as well. |
| 8 | |
| 9 | An example of such an SoC is K2G, which contains the system control hardware |
| 10 | block called Power Management Micro Controller (PMMC). This hardware block is |
| 11 | initialized early into boot process and provides services to Operating Systems |
| 12 | on multiple processors including ones running Linux. |
| 13 | |
| 14 | See http://processors.wiki.ti.com/index.php/TISCI for protocol definition. |
| 15 | |
| 16 | TI-SCI controller Device Node: |
| 17 | ============================= |
| 18 | |
| 19 | The TI-SCI node describes the Texas Instrument's System Controller entity node. |
| 20 | This parent node may optionally have additional children nodes which describe |
| 21 | specific functionality such as clocks, power domain, reset or additional |
| 22 | functionality as may be required for the SoC. This hierarchy also describes the |
| 23 | relationship between the TI-SCI parent node to the child node. |
| 24 | |
| 25 | Required properties: |
| 26 | ------------------- |
| 27 | - compatible: should be "ti,k2g-sci" |
| 28 | - mbox-names: |
| 29 | "rx" - Mailbox corresponding to receive path |
| 30 | "tx" - Mailbox corresponding to transmit path |
| 31 | |
| 32 | - mboxes: Mailboxes corresponding to the mbox-names. Each value of the mboxes |
| 33 | property should contain a phandle to the mailbox controller device |
| 34 | node and an args specifier that will be the phandle to the intended |
| 35 | sub-mailbox child node to be used for communication. |
| 36 | |
| 37 | Optional Properties: |
| 38 | ------------------- |
| 39 | - reg-names: |
| 40 | debug_messages - Map the Debug message region |
| 41 | - reg: register space corresponding to the debug_messages |
| 42 | - ti,system-reboot-controller: If system reboot can be triggered by SoC reboot |
| 43 | - ti,secure-host: If the host is defined as secure. |
| 44 | |
| 45 | Example: |
| 46 | ------------- |
| 47 | dmsc: dmsc { |
| 48 | compatible = "ti,k2g-sci"; |
| 49 | ti,host-id = <12>; |
| 50 | #address-cells = <1>; |
| 51 | #size-cells = <1>; |
| 52 | ranges; |
| 53 | } |
| 54 | |
| 55 | |
| 56 | TI-SCI Client Device Node: |
| 57 | ========================= |
| 58 | |
| 59 | Client nodes are maintained as children of the relevant TI-SCI device node. |
| 60 | |
| 61 | Example: |
| 62 | ------------- |
| 63 | dmsc: dmsc { |
| 64 | compatible = "ti,k2g-sci"; |
| 65 | ... |
| 66 | |
| 67 | my_clk_node: clk_node { |
| 68 | ... |
| 69 | ... |
| 70 | }; |
| 71 | |
| 72 | my_pd_node: pd_node { |
| 73 | ... |
| 74 | ... |
| 75 | }; |
| 76 | }; |