Lines Matching +full:sub +full:- +full:nodes
1 # SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-r5f-rproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The TI K3 family of SoCs usually have one or more dual-core Arm Cortex R5F
20 AM64x SoCs do not support LockStep mode, but rather a new non-safety mode
21 called "Single-CPU" mode, where only Core0 is used, but with ability to use
24 Each Dual-Core R5F sub-system is represented as a single DTS node
25 representing the cluster, with a pair of child DT nodes representing
37 - ti,am654-r5fss
38 - ti,j721e-r5fss
39 - ti,j7200-r5fss
40 - ti,am64-r5fss
41 - ti,j721s2-r5fss
43 power-domains:
49 "#address-cells":
52 "#size-cells":
61 # --------------------
63 ti,cluster-mode:
70 (Single-CPU mode) on AM64x SoCs, default is Split mode if omitted.
72 # R5F Processor Child Nodes:
76 "^r5f@[a-f0-9]+$":
79 The R5F Sub-System device node should define two R5F child nodes, each
83 addresses into a 32-bit address space for the processor.
85 Each R5F core has an associated 64 KB of Tightly-Coupled Memory (TCM)
86 internal memories split between two banks - TCMA and TCMB (further
94 translations between 32-bit CPU addresses into larger system bus
98 $ref: /schemas/arm/keystone/ti,k3-sci-common.yaml#
103 - ti,am654-r5f
104 - ti,j721e-r5f
105 - ti,j7200-r5f
106 - ti,am64-r5f
107 - ti,j721s2-r5f
111 - description: Address and Size of the ATCM internal memory region
112 - description: Address and Size of the BTCM internal memory region
114 reg-names:
116 - const: atcm
117 - const: btcm
125 firmware-name:
136 OMAP Mailbox specifier denoting the sub-mailbox, to be used for
138 with the sub-mailbox node used in the firmware image.
141 memory-region:
143 phandle to the reserved memory nodes to be associated with the
144 remoteproc device. There should be at least two reserved memory nodes
145 defined. The reserved memory nodes should be carveout nodes, and
146 should be defined with a "no-map" property as per the bindings in
147 Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
151 - description: region used for dynamic DMA allocations like vrings and
153 - description: region reserved for firmware image sections
158 # --------------------
161 ti,atcm-enable:
170 ti,btcm-enable:
188 $ref: /schemas/types.yaml#/definitions/phandle-array
194 phandles to one or more reserved on-chip SRAM regions. The regions
195 should be defined as child nodes of the respective SRAM node, and
200 - compatible
201 - reg
202 - reg-names
203 - ti,sci
204 - ti,sci-dev-id
205 - ti,sci-proc-ids
206 - resets
207 - firmware-name
215 - ti,am64-r5fss
218 ti,cluster-mode:
222 ti,cluster-mode:
226 - compatible
227 - power-domains
228 - "#address-cells"
229 - "#size-cells"
230 - ranges
235 - |
237 #address-cells = <2>;
238 #size-cells = <2>;
240 mailbox0: mailbox-0 {
241 #mbox-cells = <1>;
244 mailbox1: mailbox-1 {
245 #mbox-cells = <1>;
249 compatible = "simple-bus";
250 #address-cells = <2>;
251 #size-cells = <2>;
258 compatible = "simple-bus";
259 #address-cells = <2>;
260 #size-cells = <2>;
268 compatible = "ti,am654-r5fss";
269 power-domains = <&k3_pds 129>;
270 ti,cluster-mode = <1>;
271 #address-cells = <1>;
272 #size-cells = <1>;
277 compatible = "ti,am654-r5f";
280 reg-names = "atcm", "btcm";
282 ti,sci-dev-id = <159>;
283 ti,sci-proc-ids = <0x01 0xFF>;
285 firmware-name = "am65x-mcu-r5f0_0-fw";
286 ti,atcm-enable = <1>;
287 ti,btcm-enable = <1>;
290 memory-region = <&mcu_r5fss0_core0_dma_memory_region>,
296 compatible = "ti,am654-r5f";
299 reg-names = "atcm", "btcm";
301 ti,sci-dev-id = <245>;
302 ti,sci-proc-ids = <0x02 0xFF>;
304 firmware-name = "am65x-mcu-r5f0_1-fw";
305 ti,atcm-enable = <1>;
306 ti,btcm-enable = <1>;