From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 4/4] efi_loader: call smp_kick_all_cpus()
Date: Thu, 14 May 2020 20:46:34 +0200 [thread overview]
Message-ID: <94bef691-5899-8ee5-ce94-a6e5fb98dd87@gmx.de> (raw)
In-Reply-To: <20200514123831.30157-5-michael@walle.cc>
On 5/14/20 2:38 PM, Michael Walle wrote:
> On some architectures, specifically the layerscape, the secondary cores
> wait for an interrupt before entering the spin-tables. This applies only
> to boards which doesn't have PSCI provided by TF-a and u-boot does the
%s/TF-a/TF-A/, %s/u-boot/U-Boot/
> secondary cores handling.
> bootm/booti already call that function for ARM architecture; also add it
> to bootelf before switching to EL2. Additionally, provide a weak noop
> function so we don't have to have "#ifdef CONFIG_ARM64" guards.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> common/bootm.c | 9 +++++++++
> lib/efi_loader/efi_setup.c | 6 ++++++
> 2 files changed, 15 insertions(+)
>
> diff --git a/common/bootm.c b/common/bootm.c
> index db4362a643..65adf29329 100644
> --- a/common/bootm.c
> +++ b/common/bootm.c
> @@ -816,6 +816,15 @@ void __weak switch_to_non_secure_mode(void)
> {
> }
>
> +/**
> + * smp_kick_all_cpus() - kick all CPUs
> + *
> + * This routine is overridden by architectures requiring this feature.
> + */
> +void __weak smp_kick_all_cpus(void)
> +{
> +}
> +
> #else /* USE_HOSTCC */
>
> #if defined(CONFIG_FIT_SIGNATURE)
> diff --git a/lib/efi_loader/efi_setup.c b/lib/efi_loader/efi_setup.c
> index 26a7423203..7e5364adc5 100644
> --- a/lib/efi_loader/efi_setup.c
> +++ b/lib/efi_loader/efi_setup.c
> @@ -132,6 +132,12 @@ efi_status_t efi_init_obj_list(void)
> /* Allow unaligned memory access */
> allow_unaligned();
>
> + /*
> + * Some architectures need to kick secondary cores to enter their
> + * spin table.
> + */
> + smp_kick_all_cpus();
This will not compile with
CONFIG_CMD_BOOTI=n
CONFIG_CMD_BOOTM=n
CONFIG_CMD_BOOTZ=n
Best regards
Heinrich
> +
> /* On ARM switch from EL3 or secure mode to EL2 or non-secure mode */
> switch_to_non_secure_mode();
>
>
next prev parent reply other threads:[~2020-05-14 18:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 12:38 [PATCH 0/4] bootefi fixes for aarch64/layerscape Michael Walle
2020-05-14 12:38 ` [PATCH 1/4] efi_loader: aarch64: align runtime section to 64kb Michael Walle
2020-05-14 18:27 ` Heinrich Schuchardt
2020-05-14 19:04 ` Michael Walle
2020-05-14 21:03 ` Heinrich Schuchardt
2020-05-14 22:02 ` Michael Walle
2020-05-14 22:27 ` Heinrich Schuchardt
2020-05-14 23:04 ` Heinrich Schuchardt
2020-05-15 11:39 ` Michael Walle
2020-05-28 17:11 ` Heinrich Schuchardt
2020-05-14 12:38 ` [PATCH 2/4] efi_loader: check alignment in efi_add_memory_map() Michael Walle
2020-05-14 18:35 ` Heinrich Schuchardt
2020-05-14 18:50 ` Michael Walle
2020-05-14 22:02 ` Heinrich Schuchardt
2020-05-14 12:38 ` [PATCH 3/4] fsl-layerscape: align first parameter of efi_add_memory_map() Michael Walle
2020-05-14 18:39 ` Heinrich Schuchardt
2020-05-14 12:38 ` [PATCH 4/4] efi_loader: call smp_kick_all_cpus() Michael Walle
2020-05-14 18:46 ` Heinrich Schuchardt [this message]
2020-05-14 20:17 ` Alexander Graf
2020-05-14 20:35 ` Michael Walle
2020-05-16 15:54 ` Michael Walle
2020-05-18 18:30 ` Tom Rini
2020-05-18 18:45 ` Heinrich Schuchardt
2020-05-18 19:23 ` Tom Rini
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=94bef691-5899-8ee5-ce94-a6e5fb98dd87@gmx.de \
--to=xypron.glpk@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.