mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-06 21:24:29 +00:00
1e35913a26
This change implements a SMCCC transport for SCMI exchanges. This implementation follows the Linux kernel as references implementation for SCMI message processing, using the SMT format for communication channel meta-data. Use of SMCCC transport in SCMI FDT bindings are defined in the Linux kernel DT bindings since v5.8. SMCCC with SMT is implemented in OP-TEE from tag 3.9.0 [2]. Links: [2] https://github.com/OP-TEE/optee_os/commit/a58c4d706d23 Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org> Cc: Simon Glass <sjg@chromium.org> Cc: Peng Fan <peng.fan@nxp.com> Cc: Sudeep Holla <sudeep.holla@arm.com> Reviewed-by: Simon Glass <sjg@chromium.org>
19 lines
844 B
Text
19 lines
844 B
Text
config SCMI_FIRMWARE
|
|
bool "Enable SCMI support"
|
|
select FIRMWARE
|
|
select OF_TRANSLATE
|
|
depends on SANDBOX || DM_MAILBOX || ARM_SMCCC
|
|
help
|
|
System Control and Management Interface (SCMI) is a communication
|
|
protocol that defines standard interfaces for power, performance
|
|
and system management. The SCMI specification is available at
|
|
https://developer.arm.com/architectures/system-architectures/software-standards/scmi
|
|
|
|
An SCMI agent communicates with a related SCMI server firmware
|
|
located in another sub-system, as a companion micro controller
|
|
or a companion host in the CPU system.
|
|
|
|
Communications between agent (client) and the SCMI server are
|
|
based on message exchange. Messages can be exchange over tranport
|
|
channels as a mailbox device or an Arm SMCCC service with some
|
|
piece of identified shared memory.
|