Changes in Makefile

0c30714b6fa9946050adb788919d3ca9195b4803 - dm: scmi: add build control for scmi smccc and clk

Fri, 12 Nov 2021 07:49:31 +0000

dm: scmi: add build control for scmi smccc and clkThere are not scmi clk and smccc agent available for SPL/TPL.But in SPL/TPL, we still need smccc agent driver to triggerscmi uclass to setup it's all protocols, then there should bea fake plat-specific scmi clk implementation to take over theclk get/set operation from clk_scmi.c.Signed-off-by: Joseph Chen Change-Id: Ia0ebfa96b2aa6318083ddcd868af9381c74fb80c List of files: /rk3399_rockchip-uboot/drivers/firmware/Makefile

1afcdfc6b83091af305af477f46c5828c42399d8 - UPSTREAM: firmware: add SCMI agent uclass

Wed, 09 Sep 2020 16:44:00 +0000

UPSTREAM: firmware: add SCMI agent uclassThis change introduces SCMI agent uclass to interact with a firmwareusing the SCMI protocols [1].SCMI agent uclass currently supports a single method to requestprocessing of the SCMI message by an identified server. A SCMI messageis made of a byte payload associated to a protocol ID and a message ID,all defined by the SCMI specification [1]. On return from process_msg()method, the caller gets the service response.SCMI agent uclass defines a post bind generic sequence for all devices.The sequence binds all the SCMI protocols listed in the FDT for thatSCMI agent device. Currently none, but later change will introduceprotocols.This change implements a simple sandbox device for the SCMI agent uclass.The sandbox nicely answers SCMI_NOT_SUPPORTED to SCMI messages.To prepare for further test support, the sandbox exposes a architecturefunction for test application to read the sandbox emulated devices state.Currently supports 2 SCMI agents, identified by an ID in the FDT devicename. The simplistic DM test does nothing yet.SCMI agent uclass is designed for platforms that embed a SCMI server ina firmware hosted somewhere, for example in a companion co-processor orin the secure world of the executing processor. SCMI protocols allow anSCMI agent to discover and access external resources as clock, resetcontrollers and more. SCMI agent and server communicate following theSCMI specification [1]. This SCMI agent implementation complies withthe DT bindings defined in the Linux kernel source tree regardingSCMI agent description since v5.8.Links: [1] https://developer.arm.com/architectures/system-architectures/software-standards/scmiSigned-off-by: Etienne Carriere Cc: Simon Glass Cc: Peng Fan Cc: Sudeep Holla Reviewed-by: Simon Glass Conflicts: arch/sandbox/dts/test.dts configs/sandbox_defconfig drivers/firmware/Kconfig drivers/firmware/Makefile test/dm/Makefile(cherry picked from commit 358599efd827b0ee48af864537cc86facc9167c0)Signed-off-by: Joseph Chen Change-Id: I251bf48c2bb60af041e71c5904e0eb73f0243439 List of files: /rk3399_rockchip-uboot/drivers/firmware/Makefile

4f66e09bb9fbc47b73f67c3cc08ee2663e8fcdb1 - Merge branch 'master' of git://git.denx.de/u-boot

Tue, 09 May 2017 16:03:44 +0000

Merge branch 'master' of git://git.denx.de/u-bootSigned-off-by: Stefano Babic List of files: /rk3399_rockchip-uboot/drivers/firmware/Makefile

573a3811edc89c2ea3bf4fd077e3673b863b9a0d - sysreset: psci: support system reset in a generic way with PSCI

Fri, 14 Apr 2017 02:10:24 +0000

sysreset: psci: support system reset in a generic way with PSCIIf the system is running PSCI firmware, the System Reset function(func ID: 0x80000009) is supposed to be handled by PSCI, that is,the SoC/board specific reset implementation should be moved to PSCI.U-Boot should call the PSCI service according to the arm-smcccmanner.The arm-smccc is supported on ARMv7 or later. Especially, ARMv8generation SoCs are likely to run ARM Trusted Firmware BL31. Inthis case, U-Boot is a non-secure world boot loader, so it shouldnot be able to reset the system directly.Signed-off-by: Masahiro Yamada List of files: /rk3399_rockchip-uboot/drivers/firmware/Makefile