| author | Suman Anna <s-anna@ti.com> | |
| Wed, 28 Nov 2018 20:13:12 +0000 (15:13 -0500) | ||
| committer | Suman Anna <s-anna@ti.com> | |
| Wed, 27 Feb 2019 20:35:18 +0000 (14:35 -0600) | ||
| commit | a4fe48d40d2fe2e1c468e431c4a9cd09a1f589a3 | |
| tree | 1d0f826abf1a2fd27830cce1bae1529cc0f04572 | tree | snapshot (tar.xz tar.gz zip) |
| parent | 60661a1272f56415d4c0d984c27f321ec83f7e2d | commit | diff |
dt-bindings: remoteproc: Add bindings for R5F subsystem on TI K3 SoCs
The Texas Instruments K3 family of SoCs have one of more dual-core
Arm Cortex R5F processor subsystems/clusters (R5FSS). Add the device
tree bindings document for these R5F subsystem devices. These R5F
processors do not have an MMU, and so require fixed memory carveout
regions matching the firmware image addresses. The nodes require more
than one memory region, with the first memory region used for DMA
allocations at runtime. The remaining memory regions are reserved
and are used for the loading and running of the R5F remote processors.
The added example illustrates the DT nodes for the single R5FSS device
present on K3 AM65x family of SoCs.
Signed-off-by: Suman Anna <s-anna@ti.com>
The Texas Instruments K3 family of SoCs have one of more dual-core
Arm Cortex R5F processor subsystems/clusters (R5FSS). Add the device
tree bindings document for these R5F subsystem devices. These R5F
processors do not have an MMU, and so require fixed memory carveout
regions matching the firmware image addresses. The nodes require more
than one memory region, with the first memory region used for DMA
allocations at runtime. The remaining memory regions are reserved
and are used for the loading and running of the R5F remote processors.
The added example illustrates the DT nodes for the single R5FSS device
present on K3 AM65x family of SoCs.
Signed-off-by: Suman Anna <s-anna@ti.com>
| Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.txt | [new file with mode: 0644] | blob |