From: Michael Tretter <m.tretter@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Cc: Steffen Trumtrar <s.trumtrar@pengutronix.de>,
Michael Tretter <m.tretter@pengutronix.de>
Subject: [PATCH 0/2] arm: socfpga: agilex5: fix stack in entry function
Date: Wed, 13 May 2026 14:22:21 +0200 [thread overview]
Message-ID: <20260513-socfpga-agilex5-entry-v1-0-090758694c88@pengutronix.de> (raw)
The entry function for the Arrow AXE5 Eagle board places the stack at
the end of the OCRAM. However, the board firmware uses the same page for
handoff data for barebox, which is read after barebox is already
running. This may cause data corruption if the stack grows into the
handoff data.
Patch 1 fixes the stack location for the Arrow AXE5 Eagle board to avoid
corrupting the handoff data.
Patch 2 adds a ENTRY_FUNCTION_AGILEX5 macro, which uses the fixed
address for the stack and may be used by Agilex 5 based board. The
address for the stack in OCRAM is SoC specific and specifying it per
board is unnecessary and error prone.
Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
---
Michael Tretter (2):
arm: socfpga: axe5-eagle: fix stack location
arm: socfpga: agilex5: add helper for entry function
arch/arm/boards/arrow-axe5-eagle/lowlevel.c | 5 ++---
include/mach/socfpga/barebox-arm.h | 20 ++++++++++++++++++++
2 files changed, 22 insertions(+), 3 deletions(-)
---
base-commit: 2cb5e0014a37160731ad6eb6d7f7d846394db362
change-id: 20260513-socfpga-agilex5-entry-890604ad08c9
Best regards,
--
Michael Tretter <m.tretter@pengutronix.de>
next reply other threads:[~2026-05-13 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 12:22 Michael Tretter [this message]
2026-05-13 12:22 ` [PATCH 1/2] arm: socfpga: axe5-eagle: fix stack location Michael Tretter
2026-05-13 12:22 ` [PATCH 2/2] arm: socfpga: agilex5: add helper for entry function Michael Tretter
2026-05-13 14:07 ` [PATCH 0/2] arm: socfpga: agilex5: fix stack in " Sascha Hauer
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=20260513-socfpga-agilex5-entry-v1-0-090758694c88@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=s.trumtrar@pengutronix.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