summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 3c1a09e)
raw | patch | inline | side by side (parent: 3c1a09e)
author | Suman Anna <s-anna@ti.com> | |
Fri, 19 Jun 2020 20:19:03 +0000 (15:19 -0500) | ||
committer | Suman Anna <s-anna@ti.com> | |
Mon, 22 Jun 2020 15:58:16 +0000 (10:58 -0500) |
This reverts commit 71680bc1f3476e4730860e2a5900f069df0260f3.
The plain text-format binding document for the PRU remoteproc device has
been replaced by an equivalent upstream preferred YAML-format binding
document in commit d74629e20229 ("dt-bindings: remoteproc: Add binding
doc for PRU cores in the PRU-ICSS"), so revert the above text-based
binding update patch.
Signed-off-by: Suman Anna <s-anna@ti.com>
The plain text-format binding document for the PRU remoteproc device has
been replaced by an equivalent upstream preferred YAML-format binding
document in commit d74629e20229 ("dt-bindings: remoteproc: Add binding
doc for PRU cores in the PRU-ICSS"), so revert the above text-based
binding update patch.
Signed-off-by: Suman Anna <s-anna@ti.com>
Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.txt | patch | blob | history |
diff --git a/Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.txt b/Documentation/devicetree/bindings/remoteproc/ti,pru-rproc.txt
index 0460f27847ec10d966ffb1ab5ffe05740f537a63..6d1d290c4c7234126bbaa6d857cbbd6c0ff4af7a 100644 (file)
-PRU/RTU/Tx_PRU Core on TI SoCs
-==============================
+PRU Core on TI SoCs
+===================
Each PRUSS has dual PRU cores, each represented by a PRU node. Each PRU core
has a dedicated Instruction RAM, Control and Debug register sets, and use
the Data RAMs present within the PRUSS for code execution.
-The K3 SoCs containing ICSSG v1.0 (eg: AM65x) have two additional PRU cores
-called RTUs with slightly different IP integration. The K3 SoCs containing
-the revised ICSSG v1.1 (eg: J721E) have an extra two auxiliary PRU cores
-called Tx_PRUs that augment the PRUs. Each RTU or Tx_PRU core can be used
-independently like a PRU, or alongside a corresponding PRU core to
-provide/implement auxiliary functionality/support.
-
-Each PRU, RTU or Tx_PRU core node should be defined as a child node of the
-corresponding PRUSS node. Each node can optionally be rendered inactive by
-using the standard DT string property, "status".
+Each PRU core node should be defined as a child node of the corresponding PRUSS
+node. Each node can optionally be rendered inactive by using the standard DT
+string property, "status".
Please see the overall PRUSS bindings document for additional details
including a complete example,
"ti,am4376-pru" for AM437x family of SoCs
"ti,am5728-pru" for AM57xx family of SoCs
"ti,k2g-pru" for 66AK2G family of SoCs
- "ti,am654-pru" for PRUs in K3 AM65x family of SoCs
- "ti,am654-rtu" for RTUs in K3 AM65x family of SoCs
- "ti,j721e-pru" for PRUs in K3 J721E family of SoCs
- "ti,j721e-rtu" for RTUs in K3 J721E family of SoCs
- "ti,j721e-tx-pru" for Tx_PRUs in K3 J721E family of SoCs
- reg : base address and size for each of the 3 sub-module address
spaces as mentioned in reg-names, and in the same order as
the reg-names