From: Tom Rini Date: Fri, 8 Mar 2019 13:09:53 -0500 Subject: [U-Boot] [PATCH v1 0/2] Allow platform specific service handling on PSCI In-Reply-To: <1549960023-124134-1-git-send-email-chee.hong.ang@intel.com> References: <1549960023-124134-1-git-send-email-chee.hong.ang@intel.com> Message-ID: <20190308180953.GH5026@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tue, Feb 12, 2019 at 12:27:01AM -0800, chee.hong.ang at intel.com wrote: > From: "Ang, Chee Hong" > > 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 > #include > #include > #include > #include > > #define PSCI_SMC64_FUNC_ID1 0xC2000001 > #define PSCI_SMC64_FUNC_ID2 0xC2000002 > > static void __secure psci_plat_specific_func1(unsigned long function_id) > { > /* Your code for handling the SMC/PSCI platform specific service 1 */ > } > > static void __secure psci_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); > > Ang, Chee Hong (1): > ARMv8: Disable fwcall when PSCI is enabled > > Chee 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? -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: