Lines Matching +full:atcm +full:- +full:enable
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 Each Dual-Core R5F sub-system is represented as a single DTS node
23 properties that enable the OS running on the host processor to perform
33 - ti,am654-r5fss
34 - ti,j721e-r5fss
36 power-domains:
42 "#address-cells":
45 "#size-cells":
54 # --------------------
56 ti,cluster-mode:
68 "^r5f@[a-f0-9]+$":
71 The R5F Sub-System device node should define two R5F child nodes, each
75 addresses into a 32-bit address space for the processor.
77 Each R5F core has an associated 64 KB of Tightly-Coupled Memory (TCM)
78 internal memories split between two banks - TCMA and TCMB (further
80 ATCM and BTCM) provide read/write performance on par with the core's L1
86 translations between 32-bit CPU addresses into larger system bus
91 - $ref: /schemas/arm/keystone/ti,k3-sci-common.yaml#
96 - ti,am654-r5f
97 - ti,j721e-r5f
101 - description: Address and Size of the ATCM internal memory region
102 - description: Address and Size of the BTCM internal memory region
104 reg-names:
106 - const: atcm
107 - const: btcm
115 firmware-name:
126 OMAP Mailbox specifier denoting the sub-mailbox, to be used for
128 with the sub-mailbox node used in the firmware image.
131 memory-region:
136 should be defined with a "no-map" property as per the bindings in
137 Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
141 - description: region used for dynamic DMA allocations like vrings and
143 - description: region reserved for firmware image sections
148 # --------------------
151 ti,atcm-enable:
155 R5F core configuration mode dictating if ATCM should be enabled. The
156 R5F address of ATCM is dictated by ti,loczrama property. Should be
158 if omitted. Recommended to enable it for maximizing TCMs.
160 ti,btcm-enable:
174 address 0 (from core's view). Should be either a value of 1 (ATCM
178 $ref: /schemas/types.yaml#/definitions/phandle-array
182 phandles to one or more reserved on-chip SRAM regions. The regions
188 - compatible
189 - reg
190 - reg-names
191 - ti,sci
192 - ti,sci-dev-id
193 - ti,sci-proc-ids
194 - resets
195 - firmware-name
200 - compatible
201 - power-domains
202 - "#address-cells"
203 - "#size-cells"
204 - ranges
209 - |
212 compatible = "ti,am654-evm", "ti,am654";
213 #address-cells = <2>;
214 #size-cells = <2>;
217 compatible = "simple-bus";
218 #address-cells = <2>;
219 #size-cells = <2>;
226 compatible = "simple-bus";
227 #address-cells = <2>;
228 #size-cells = <2>;
236 compatible = "ti,am654-r5fss";
237 power-domains = <&k3_pds 129>;
238 ti,cluster-mode = <1>;
239 #address-cells = <1>;
240 #size-cells = <1>;
245 compatible = "ti,am654-r5f";
248 reg-names = "atcm", "btcm";
250 ti,sci-dev-id = <159>;
251 ti,sci-proc-ids = <0x01 0xFF>;
253 firmware-name = "am65x-mcu-r5f0_0-fw";
254 ti,atcm-enable = <1>;
255 ti,btcm-enable = <1>;
258 memory-region = <&mcu_r5fss0_core0_dma_memory_region>,
264 compatible = "ti,am654-r5f";
267 reg-names = "atcm", "btcm";
269 ti,sci-dev-id = <245>;
270 ti,sci-proc-ids = <0x02 0xFF>;
272 firmware-name = "am65x-mcu-r5f0_1-fw";
273 ti,atcm-enable = <1>;
274 ti,btcm-enable = <1>;