1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 $id: http://devicetree.org/schemas/soc/ti/ti,pruss.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 TI Programmable Real-Time Unit and Industrial Communication Subsystem
11 - Suman Anna <s-anna@ti.com>
15 The Programmable Real-Time Unit and Industrial Communication Subsystem
16 (PRU-ICSS a.k.a. PRUSS) is present on various TI SoCs such as AM335x, AM437x,
17 Keystone 66AK2G, OMAP-L138/DA850 etc. A PRUSS consists of dual 32-bit RISC
18 cores (Programmable Real-Time Units, or PRUs), shared RAM, data and
19 instruction RAMs, some internal peripheral modules to facilitate industrial
20 communication, and an interrupt controller.
22 The programmable nature of the PRUs provide flexibility to implement custom
23 peripheral interfaces, fast real-time responses, or specialized data handling.
24 The common peripheral modules include the following,
25 - an Ethernet MII_RT module with two MII ports
26 - an MDIO port to control external Ethernet PHYs
27 - an Industrial Ethernet Peripheral (IEP) to manage/generate Industrial
29 - an Enhanced Capture Module (eCAP)
30 - an Industrial Ethernet Timer with 7/9 capture and 16 compare events
31 - a 16550-compatible UART to support PROFIBUS
32 - Enhanced GPIO with async capture and serial support
34 A PRU-ICSS subsystem can have up to three shared data memories. A PRU core
35 acts on a primary Data RAM (there are usually 2 Data RAMs) at its address
36 0x0, but also has access to a secondary Data RAM (primary to the other PRU
37 core) at its address 0x2000. A shared Data RAM, if present, can be accessed
38 by both the PRU cores. The Interrupt Controller (INTC) and a CFG module are
39 common to both the PRU cores. Each PRU core also has a private instruction
40 RAM, and specific register spaces for Control and Debug functionalities.
42 Various sub-modules within a PRU-ICSS subsystem are represented as individual
43 nodes and are defined using a parent-child hierarchy depending on their
44 integration within the IP and the SoC. These nodes are described in the
50 Each PRU-ICSS instance is represented as its own node with the individual PRU
51 processor cores, the memories node, an INTC node and an MDIO node represented
52 as child nodes within this PRUSS node. This node shall be a child of the
53 corresponding interconnect bus nodes or target-module nodes.
55 See ../../mfd/syscon.yaml for generic SysCon binding details.
60 pattern: "^(pruss|icssg)@[0-9a-f]+$"
64 - ti,am3356-pruss # for AM335x SoC family
65 - ti,am4376-pruss0 # for AM437x SoC family and PRUSS unit 0
66 - ti,am4376-pruss1 # for AM437x SoC family and PRUSS unit 1
67 - ti,am5728-pruss # for AM57xx SoC family
68 - ti,k2g-pruss # for 66AK2G SoC family
69 - ti,am654-icssg # for K3 AM65x SoC family
70 - ti,j721e-icssg # for K3 J721E SoC family
86 This property is as per sci-pm-domain.txt.
92 The various Data RAMs within a single PRU-ICSS unit are represented as a
93 single node with the name 'memories'.
99 minItems: 2 # On AM437x one of two PRUSS units don't contain Shared RAM.
102 - description: Address and size of the Data RAM0.
103 - description: Address and size of the Data RAM1.
105 Address and size of the Shared Data RAM. Note that on AM437x one
106 of two PRUSS units don't contain Shared RAM, while the second one
121 additionalProperties: false
125 PRU-ICSS configuration space. CFG sub-module represented as a SysCon.
132 - const: ti,pruss-cfg
158 coreclk-mux@[a-f0-9]+$:
160 This is applicable only for ICSSG (K3 SoCs). The ICSSG modules
161 core clock can be set to one of the 2 sources: ICSSG_CORE_CLK or
162 ICSSG_ICLK. This node models this clock mux and should have the
173 - description: ICSSG_CORE Clock
174 - description: ICSSG_ICLK Clock
179 assigned-clock-parents:
182 Standard assigned-clocks-parents definition used for selecting
183 mux parent (one of the mux input).
191 additionalProperties: false
193 iepclk-mux@[a-f0-9]+$:
195 The IEP module can get its clock from 2 sources: ICSSG_IEP_CLK or
196 CORE_CLK (OCP_CLK in older SoCs). This node models this clock
197 mux and should have the name "iepclk-mux".
207 - description: ICSSG_IEP Clock
208 - description: Core Clock (OCP Clock in older SoCs)
213 assigned-clock-parents:
216 Standard assigned-clocks-parents definition used for selecting
217 mux parent (one of the mux input).
225 additionalProperties: false
227 additionalProperties: false
231 Industrial Ethernet Peripheral to manage/generate Industrial Ethernet
232 functions such as time stamping. Each PRUSS has either 1 IEP (on AM335x,
233 AM437x, AM57xx & 66AK2G SoCs) or 2 IEPs (on K3 AM65x & J721E SoCs ). IEP
234 is used for creating PTP clocks and generating PPS signals.
240 Real-Time Ethernet to support multiple industrial communication protocols.
241 MII-RT sub-module represented as a SysCon.
248 - const: ti,pruss-mii
254 additionalProperties: false
258 The Real-time Media Independent Interface to support multiple industrial
259 communication protocols (G stands for Gigabit). MII-G-RT sub-module
260 represented as a SysCon.
267 - const: ti,pruss-mii-g
273 additionalProperties: false
275 interrupt-controller@[a-f0-9]+$:
277 PRUSS INTC Node. Each PRUSS has a single interrupt controller instance
278 that is common to all the PRU cores. This should be represented as an
279 interrupt-controller node.
285 MDIO Node. Each PRUSS has an MDIO module that can be used to control
286 external PHYs. The MDIO module used within the PRU-ICSS is an instance of
287 the MDIO Controller used in TI Davinci SoCs.
290 - $ref: /schemas/net/ti,davinci-mdio.yaml#
294 "^(pru|rtu|txpru)@[0-9a-f]+$":
296 PRU Node. Each PRUSS has dual PRU cores, each represented as a RemoteProc
297 device through a PRU child node each. Each node can optionally be rendered
298 inactive by using the standard DT string property, "status". The ICSSG IP
299 present on K3 SoCs have additional auxiliary PRU cores with slightly
300 different IP integration.
309 additionalProperties: false
311 # Due to inability of correctly verifying sub-nodes with an @address through
312 # the "required" list, the required sub-nodes below are commented out for now.
316 # - interrupt-controller
334 /* Example 1 AM33xx PRU-ICSS */
336 compatible = "ti,am3356-pruss";
338 #address-cells = <1>;
342 pruss_mem: memories@0 {
346 reg-names = "dram0", "dram1", "shrdram2";
349 pruss_cfg: cfg@26000 {
350 compatible = "ti,pruss-cfg", "syscon";
351 #address-cells = <1>;
353 reg = <0x26000 0x2000>;
354 ranges = <0x00 0x26000 0x2000>;
357 #address-cells = <1>;
360 pruss_iepclk_mux: iepclk-mux@30 {
363 clocks = <&l3_gclk>, /* icss_iep */
364 <&pruss_ocp_gclk>; /* icss_ocp */
369 pruss_mii_rt: mii-rt@32000 {
370 compatible = "ti,pruss-mii", "syscon";
371 reg = <0x32000 0x58>;
374 pruss_mdio: mdio@32400 {
375 compatible = "ti,davinci_mdio";
376 reg = <0x32400 0x90>;
377 clocks = <&dpll_core_m4_ck>;
379 bus_freq = <1000000>;
380 #address-cells = <1>;
387 /* Example 2 AM43xx PRU-ICSS with PRUSS1 node */
388 #include <dt-bindings/interrupt-controller/arm-gic.h>
390 compatible = "ti,am4376-pruss1";
392 #address-cells = <1>;
396 pruss1_mem: memories@0 {
400 reg-names = "dram0", "dram1", "shrdram2";
403 pruss1_cfg: cfg@26000 {
404 compatible = "ti,pruss-cfg", "syscon";
405 #address-cells = <1>;
407 reg = <0x26000 0x2000>;
408 ranges = <0x00 0x26000 0x2000>;
411 #address-cells = <1>;
414 pruss1_iepclk_mux: iepclk-mux@30 {
417 clocks = <&sysclk_div>, /* icss_iep */
418 <&pruss_ocp_gclk>; /* icss_ocp */
423 pruss1_mii_rt: mii-rt@32000 {
424 compatible = "ti,pruss-mii", "syscon";
425 reg = <0x32000 0x58>;
428 pruss1_mdio: mdio@32400 {
429 compatible = "ti,davinci_mdio";
430 reg = <0x32400 0x90>;
431 clocks = <&dpll_core_m4_ck>;
433 bus_freq = <1000000>;
434 #address-cells = <1>;