summaryrefslogtreecommitdiffstats
path: root/.mailmap
diff options
context:
space:
mode:
authorMartyn Welch <martyn.welch@collabora.com>2024-08-02 17:21:03 +0200
committerMathieu Poirier <mathieu.poirier@linaro.org>2024-08-21 19:22:54 +0200
commitebcf9008a895a2a9416f69e186b56fbade35e12c (patch)
treed6c9285b0132e4467b87739a276e75545a5665d2 /.mailmap
parentremoteproc: k3: Factor out TI-SCI processor control OF get function (diff)
downloadlinux-ebcf9008a895a2a9416f69e186b56fbade35e12c.tar.xz
linux-ebcf9008a895a2a9416f69e186b56fbade35e12c.zip
remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem
The AM62x and AM64x SoCs of the TI K3 family has a Cortex M4F core in the MCU domain. This core is typically used for safety applications in a stand alone mode. However, some application (non safety related) may want to use the M4F core as a generic remote processor with IPC to the host processor. The M4F core has internal IRAM and DRAM memories and are exposed to the system bus for code and data loading. A remote processor driver is added to support this subsystem, including being able to load and boot the M4F core. Loading includes to M4F internal memories and predefined external code/data memories. The carve outs for external contiguous memory is defined in the M4F device node and should match with the external memory declarations in the M4F image binary. The M4F subsystem has two resets. One reset is for the entire subsystem i.e including the internal memories and the other, a local reset is only for the M4F processing core. When loading the image, the driver first releases the subsystem reset, loads the firmware image and then releases the local reset to let the M4F processing core run. Signed-off-by: Martyn Welch <martyn.welch@collabora.com> Signed-off-by: Hari Nagalla <hnagalla@ti.com> Signed-off-by: Andrew Davis <afd@ti.com> Tested-by: Wadim Egorov <w.egorov@phytec.de> Link: https://lore.kernel.org/r/20240802152109.137243-4-afd@ti.com Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions