Allow platform specific service handling on PSCI
Get series with b4
b4 am 20190308180953.GH5026@bill-the-catVersions newest first
- v1 Latest0 of 2 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [U-Boot] [PATCH v1 0/2] Allow platform specific service handling on PSCI
Quoted 38 lines · chee.hong.ang at intel.com
From: "Ang, Chee Hong" <[email protected]>
Currently u-boot only support standard PSCI functions for power management and lack of convenient method to allow the users to extend the PSCI functions to support platform specific services. Most of the u-boot users still rely on ATF (ARM Trusted Firmware) to handle the standard power management and platform specific PSCI services.
The purpose of this patchsets is to allow u-boot users to support their own platform specific secure SMC/PSCI services without making any SMC calls to ATF. This will benefit the users who need to use u-boot as the only bootloader and secure service provider without relying on ATF.Below is a simple code example for adding your own PSCI functions:
#include <
common.h>
#include <errno.h>
#include <asm/io.h>
#include <asm/psci.h>
#include <asm/secure.h>#define
PSCI_SMC64_FUNC_ID10xC2000001
#definePSCI_SMC64_FUNC_ID20xC2000002static void
__securepsci_plat_specific_func1(unsigned long function_id){ /* Your code for handling the SMC/PSCI platform specific service 1 */ }static void
__securepsci_plat_specific_func2(unsigned long function_id){ /* Your code for handling the SMC/PSCI platform specific service 2 */ }DECLARE_SECURE_SVC(plat_specific_func1,
PSCI_SMC64_FUNC_ID1,psci_plat_specific_func1); DECLARE_SECURE_SVC(plat_specific_func2, PSCI_SMC64_FUNC_ID2, psci_plat_specific_func2);
Quoted 5 lines
Ang, Chee Hong (1):
ARMv8: Disable fwcall when PSCI is enabledChee Hong Ang (1):
ARMv8: Allow SiP service extensions on top of PSCI code
Conceptually, I suppose this is a logical step. In specifics, would we want to make this functionality opt-in, or no, that doesn't make sense?
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190308/9b2218d5/attachment.sig>