From: "Leif Lindholm" <quic_llindhol@quicinc.com>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Cc: <devel@edk2.groups.io>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Sami Mujawar <sami.mujawar@arm.com>
Subject: Re: [PATCH v2 1/1] ArmPkg: add SMC defines for SiP service calls
Date: Fri, 2 Jun 2023 12:40:49 +0100 [thread overview]
Message-ID: <ZHnVQXv7qHUpGGc/@qc-i7.hemma.eciton.net> (raw)
In-Reply-To: <20230601171425.314391-1-marcin.juszkiewicz@linaro.org>
On Thu, Jun 01, 2023 at 19:14:25 +0200, Marcin Juszkiewicz wrote:
> They are useful for those platforms where SMC SiP calls exist.
>
> Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Thanks, merged as 4354c22f3877.
> ---
> ArmPkg/Include/IndustryStandard/ArmStdSmc.h | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/ArmPkg/Include/IndustryStandard/ArmStdSmc.h b/ArmPkg/Include/IndustryStandard/ArmStdSmc.h
> index 374b9ded7f5f..616c650d07c8 100644
> --- a/ArmPkg/Include/IndustryStandard/ArmStdSmc.h
> +++ b/ArmPkg/Include/IndustryStandard/ArmStdSmc.h
> @@ -244,4 +244,13 @@
> #define TRNG_STATUS_INVALID_PARAMETER (INT32)(-2)
> #define TRNG_STATUS_NO_ENTROPY (INT32)(-3)
>
> +/*
> + * SMC64 SiP Service Calls
> + */
> +
> +#define SMC_FASTCALL 0x80000000
> +#define SMC64_FUNCTION (SMC_FASTCALL | 0x40000000)
> +#define SMC_SIP_FUNCTION (SMC64_FUNCTION | 0x02000000)
> +#define SMC_SIP_FUNCTION_ID(n) (SMC_SIP_FUNCTION | (n))
> +
> #endif // ARM_STD_SMC_H_
> --
> 2.40.1
>
next prev parent reply other threads:[~2023-06-02 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 17:14 [PATCH v2 1/1] ArmPkg: add SMC defines for SiP service calls Marcin Juszkiewicz
2023-06-02 11:40 ` Leif Lindholm [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-05 6:37 [PATCH v2 0/8] ArmCpuInfo improvements Marcin Juszkiewicz
2023-06-05 6:37 ` [PATCH v2 1/1] ArmPkg: add SMC defines for SiP service calls Marcin Juszkiewicz
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-list 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=ZHnVQXv7qHUpGGc/@qc-i7.hemma.eciton.net \
--to=devel@edk2.groups.io \
/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