remoteproc: Introduce K3 system controller
authorLokesh Vutla <lokeshvutla@ti.com>
Mon, 27 Aug 2018 10:27:51 +0000 (15:57 +0530)
committerTom Rini <trini@konsulko.com>
Tue, 11 Sep 2018 12:32:55 +0000 (08:32 -0400)
commit1ad190bf5936ad87d0bd80ecf55a1ce09e9d3ae9
tree025b2f40776d6c803ea4f896d3e3d96059e19a00
parent81ae6e6d0098c9ad7d6746b4f2952a046130999c
remoteproc: Introduce K3 system controller

K3 specific SoCs have a dedicated microcontroller for doing
resource management. Any HLOS/firmware on compute clusters should
load a firmware to this microcontroller before accessing any resource.
Adding support for loading this firmware.

After the K3 system controller got loaded with firmware and started
up it sends out a boot notification message through the secure proxy
facility using the TI SCI protocol. Intercept and receive this message
through the rproc start operation which will need to get invoked
explicitly after the firmware got loaded.

Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
doc/device-tree-bindings/remoteproc/k3-system-controller.txt [new file with mode: 0644]
drivers/remoteproc/Kconfig
drivers/remoteproc/Makefile
drivers/remoteproc/k3_system_controller.c [new file with mode: 0644]