mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-06 21:24:29 +00:00
1ad190bf59
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>
24 lines
734 B
Text
24 lines
734 B
Text
Texas Instruments' 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.
|
|
This driver communicates with ROM for loading this firmware.
|
|
|
|
Required properties:
|
|
--------------------
|
|
- compatible: Shall be: "ti,am654-system-controller"
|
|
- mbox-names: "tx" for Transfer channel
|
|
"rx" for Receive channel
|
|
- mboxes: Corresponding phandles to mailbox channels.
|
|
|
|
|
|
Example:
|
|
--------
|
|
|
|
system-controller: system-controller {
|
|
compatible = "ti,am654-system-controller";
|
|
mboxes= <&secproxy 4>, <&secproxy 5>;
|
|
mbox-names = "tx", "rx";
|
|
};
|