From: Andre Przywara <andre.przywara@arm.com>
To: Samuel Holland <samuel@sholland.org>
Cc: u-boot@lists.denx.de, Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [PATCH] sunxi: A23/A33/H3: Actually move the secure monitor
Date: Mon, 25 Oct 2021 15:08:56 +0100 [thread overview]
Message-ID: <20211025150856.2f496330@slackpad.fritz.box> (raw)
In-Reply-To: <20211012235457.24615-1-samuel@sholland.org>
On Tue, 12 Oct 2021 18:54:56 -0500
Samuel Holland <samuel@sholland.org> wrote:
> commit 1ebfc0c631e3 ("sunxi: A23/A33/H3: Move sun8i secure monitor to
> SRAM A2") attempted to move the secure monitor to SRAM A2. But not all
> sun8i SoCs have SRAM A2, so a check was put in for SUNXI_SRAM_A2_SIZE to
> avoid breaking the other SoCs.
>
> However, because the header providing SUNXI_SRAM_A2_SIZE was not
> included, this unintentionally skipped the new definitions on all SoCs.
> Fix this by including the right header.
>
> Fixes: 1ebfc0c631e3 ("sunxi: A23/A33/H3: Move sun8i secure monitor to SRAM A2")
> Signed-off-by: Samuel Holland <samuel@sholland.org>
Indeed. Weird, I thought I checked the readelf output.
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Cheers,
Andre
> ---
>
> include/configs/sun8i.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/configs/sun8i.h b/include/configs/sun8i.h
> index 27c9808a49..5636356366 100644
> --- a/include/configs/sun8i.h
> +++ b/include/configs/sun8i.h
> @@ -12,6 +12,8 @@
> * A23 specific configuration
> */
>
> +#include <asm/arch/cpu.h>
> +
> #ifdef SUNXI_SRAM_A2_SIZE
> /*
> * If the SoC has enough SRAM A2, use that for the secure monitor.
prev parent reply other threads:[~2021-10-25 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 23:54 [PATCH] sunxi: A23/A33/H3: Actually move the secure monitor Samuel Holland
2021-10-25 14:08 ` Andre Przywara [this message]
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=20211025150856.2f496330@slackpad.fritz.box \
--to=andre.przywara@arm.com \
--cc=jagan@amarulasolutions.com \
--cc=samuel@sholland.org \
--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