39d383bdac
Add Arm FF-A support implementing Arm Firmware Framework for Armv8-A v1.0 The Firmware Framework for Arm A-profile processors (FF-A v1.0) [1] describes interfaces (ABIs) that standardize communication between the Secure World and Normal World leveraging TrustZone technology. This driver uses 64-bit registers as per SMCCCv1.2 spec and comes on top of the SMCCC layer. The driver provides the FF-A ABIs needed for querying the FF-A framework from the secure world. The driver uses SMC32 calling convention which means using the first 32-bit data of the Xn registers. All supported ABIs come with their 32-bit version except FFA_RXTX_MAP which has 64-bit version supported. Both 32-bit and 64-bit direct messaging are supported which allows both 32-bit and 64-bit clients to use the FF-A bus. FF-A is a discoverable bus and similar to architecture features. FF-A bus is discovered using ARM_SMCCC_FEATURES mechanism performed by the PSCI driver. Clients are able to probe then use the FF-A bus by calling the DM class searching APIs (e.g: uclass_first_device). The Secure World is considered as one entity to communicate with using the FF-A bus. FF-A communication is handled by one device and one instance (the bus). This FF-A driver takes care of all the interactions between Normal world and Secure World. The driver exports its operations to be used by upper layers. Exported operations: - ffa_partition_info_get - ffa_sync_send_receive - ffa_rxtx_unmap Generic FF-A methods are implemented in the Uclass (arm-ffa-uclass.c). Arm specific methods are implemented in the Arm driver (arm-ffa.c). For more details please refer to the driver documentation [2]. [1]: https://developer.arm.com/documentation/den0077/latest/ [2]: doc/arch/arm64.ffa.rst Signed-off-by: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Ilias Apalodimas <ilias.apalodimas@linaro.org> Cc: Tom Rini <trini@konsulko.com> Cc: Jens Wiklander <jens.wiklander@linaro.org> Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>
50 lines
1.4 KiB
Plaintext
50 lines
1.4 KiB
Plaintext
config FIRMWARE
|
|
bool "Enable Firmware driver support"
|
|
|
|
config SPL_FIRMWARE
|
|
bool "Enable Firmware driver support in SPL"
|
|
depends on FIRMWARE && SPL
|
|
|
|
config SPL_ARM_PSCI_FW
|
|
bool
|
|
select SPL_FIRMWARE
|
|
|
|
config ARM_PSCI_FW
|
|
bool
|
|
select FIRMWARE
|
|
|
|
config TI_SCI_PROTOCOL
|
|
tristate "TI System Control Interface (TISCI) Message Protocol"
|
|
depends on K3_SEC_PROXY
|
|
select FIRMWARE
|
|
select SPL_FIRMWARE if SPL
|
|
help
|
|
TI System Control Interface (TISCI) Message Protocol is used to manage
|
|
compute systems such as ARM, DSP etc with the system controller in
|
|
complex System on Chip (SoC) such as those found on certain K3
|
|
generation SoC from TI.
|
|
|
|
This protocol library is used by client drivers to use the features
|
|
provided by the system controller.
|
|
|
|
config ZYNQMP_FIRMWARE
|
|
bool "ZynqMP Firmware interface"
|
|
select FIRMWARE
|
|
help
|
|
Firmware interface driver is used by different
|
|
drivers to communicate with the firmware for
|
|
various platform management services.
|
|
Say yes to enable ZynqMP firmware interface driver.
|
|
If in doubt, say N.
|
|
|
|
config ARM_SMCCC_FEATURES
|
|
bool "Arm SMCCC features discovery"
|
|
depends on ARM_PSCI_FW
|
|
help
|
|
Discover Arm SMCCC features for which a U-Boot driver is defined. When enabled,
|
|
the PSCI driver is always probed and binds dirvers registered to the Arm SMCCC
|
|
services if any and reported as supported by the SMCCC firmware.
|
|
|
|
source "drivers/firmware/arm-ffa/Kconfig"
|
|
source "drivers/firmware/scmi/Kconfig"
|