From: Ang, Chee Hong <chee.hong.ang@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 0/2] Allow platform specific service handling on PSCI
Date: Tue, 5 Mar 2019 07:18:23 +0000 [thread overview]
Message-ID: <1551770303.19143.3.camel@intel.com> (raw)
In-Reply-To: <1549960023-124134-1-git-send-email-chee.hong.ang@intel.com>
On Tue, 2019-02-12 at 00:27 -0800, chee.hong.ang at intel.com wrote:
> From: "Ang, Chee Hong" <chee.hong.ang@intel.com>
Hi Tom/Albert,
Any comment on this patch ?
Best Regards,
Ang
>
> 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_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
>
> arch/arm/cpu/armv8/Makefile | 2 ++
> arch/arm/cpu/armv8/psci.S | 33 +++++++++++++++++++++++++++------
> arch/arm/cpu/armv8/u-boot.lds | 4 ++++
> arch/arm/include/asm/secure.h | 31 +++++++++++++++++++++++++++++++
> 4 files changed, 64 insertions(+), 6 deletions(-)
>
next prev parent reply other threads:[~2019-03-05 7:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 8:27 [U-Boot] [PATCH v1 0/2] Allow platform specific service handling on PSCI chee.hong.ang at intel.com
2019-02-12 8:27 ` [U-Boot] [PATCH v1 1/2] ARMv8: Allow SiP service extensions on top of PSCI code chee.hong.ang at intel.com
2019-04-24 13:22 ` [U-Boot] [U-Boot, v1, " Tom Rini
2019-02-12 8:27 ` [U-Boot] [PATCH v1 2/2] ARMv8: Disable fwcall when PSCI is enabled chee.hong.ang at intel.com
2019-04-24 13:22 ` [U-Boot] [U-Boot, v1, " Tom Rini
2019-02-14 8:53 ` [U-Boot] [PATCH v1 0/2] Allow platform specific service handling on PSCI Ang, Chee Hong
2019-03-05 7:18 ` Ang, Chee Hong [this message]
2019-03-08 18:09 ` Tom Rini
2019-03-11 15:27 ` Ang, Chee Hong
2019-03-11 19:48 ` Tom Rini
2019-03-13 8:10 ` Ang, Chee Hong
2019-03-13 16:01 ` Tom Rini
2019-04-23 5:51 ` Ang, Chee Hong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1551770303.19143.3.camel@intel.com \
--to=chee.hong.ang@intel.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox