From: Lucas Tanure <tanure@linux.com>
To: u-boot@lists.u-boot-project.org
Cc: neil.armstrong@linaro.org, trini@konsulko.com,
ilias.apalodimas@linaro.org, funderscore@postmasteros.org,
u-boot-amlogic@groups.io, Lucas Tanure <tanure@linux.com>
Subject: [PATCH 2/4] arm: meson: add Amlogic T7 SoC family support
Date: Thu, 6 Aug 2026 11:18:07 +0100 [thread overview]
Message-ID: <20260806101809.72526-3-tanure@linux.com> (raw)
In-Reply-To: <20260806101809.72526-1-tanure@linux.com>
Add initial support for the Amlogic T7 family (A311D2). U-Boot runs
as BL33, loaded at address 0x0 and entered from the vendor BL31 at
EL2, either uncompressed or LZ4-compressed inside the boot image (the
BL31 decompresses it).
The secure firmware writes the SCS device keys into the first page of
the loaded BL33 image (2 KiB for the BL33 key followed by 2 KiB for
the kernel key). Reserve that page with a boot0 hook, as the vendor
U-Boot does, so the keys do not overwrite U-Boot's entry code.
The firmware also enters BL33 with the non-secure watchdog running:
disable it in board_init(), otherwise the board is reset about a
minute after boot.
The memory map leaves 0x05100000 - 0x09000000 unmapped: the secure
world owns this span (the BL31 and BL32 runtime zones described in
the upstream devicetree, plus further firmware-protected pages), and
this matches the vendor bootloader's own map. The whole span is also
added to the devicetree and EFI reserved memory at boot time so no
allocation is placed in memory U-Boot cannot access.
get_effective_memsize() is capped at 0xdf800000 because the top 8 MiB
of the first DRAM bank contain pages the secure world protects at
runtime; U-Boot and its heap must stay below them.
Assisted-by: Claude:claude-fable-5
Signed-off-by: Lucas Tanure <tanure@linux.com>
---
arch/arm/include/asm/arch-meson/boot0.h | 18 +++++
arch/arm/mach-meson/Kconfig | 10 +++
arch/arm/mach-meson/Makefile | 1 +
arch/arm/mach-meson/board-t7.c | 97 +++++++++++++++++++++++++
4 files changed, 126 insertions(+)
create mode 100644 arch/arm/include/asm/arch-meson/boot0.h
create mode 100644 arch/arm/mach-meson/board-t7.c
diff --git a/arch/arm/include/asm/arch-meson/boot0.h b/arch/arm/include/asm/arch-meson/boot0.h
new file mode 100644
index 00000000000..3ec085ccd64
--- /dev/null
+++ b/arch/arm/include/asm/arch-meson/boot0.h
@@ -0,0 +1,18 @@
+/* SPDX-License-Identifier: GPL-2.0+ */
+/*
+ * (C) Copyright 2026 Lucas Tanure <tanure@linux.com>
+ */
+
+#ifndef __MESON_BOOT0_H
+#define __MESON_BOOT0_H
+
+/*
+ * The T7-family secure firmware writes the SCS device keys into the
+ * first page of the loaded BL33 image (2048 bytes for the BL33 key
+ * followed by 2048 bytes for the kernel key). Keep that page reserved
+ * so the keys do not overwrite U-Boot's entry code.
+ */
+ b reset
+ .space 4096
+
+#endif /* __MESON_BOOT0_H */
diff --git a/arch/arm/mach-meson/Kconfig b/arch/arm/mach-meson/Kconfig
index c687ef822a2..40aafc0b922 100644
--- a/arch/arm/mach-meson/Kconfig
+++ b/arch/arm/mach-meson/Kconfig
@@ -67,6 +67,15 @@ config MESON_A1
help
Select this if your SoC is an A113L
+config MESON_T7
+ bool "T7"
+ select MESON64_COMMON
+ select ENABLE_ARM_SOC_BOOT0_HOOK
+ imply OF_UPSTREAM
+ help
+ Select this if your SoC is from the Amlogic T7 family, like
+ the A311D2 found on the Khadas VIM4 board.
+
endchoice
config SYS_SOC
@@ -91,6 +100,7 @@ config SYS_BOARD
default "q200" if MESON_GXM
default "s400" if MESON_AXG
default "u200" if MESON_G12A
+ default "vim4" if MESON_T7
default ""
help
This option contains information about board name.
diff --git a/arch/arm/mach-meson/Makefile b/arch/arm/mach-meson/Makefile
index 08a24d4b24f..dc2bc0ceecb 100644
--- a/arch/arm/mach-meson/Makefile
+++ b/arch/arm/mach-meson/Makefile
@@ -17,3 +17,4 @@ endif
obj-$(CONFIG_MESON_AXG) += board-axg.o
obj-$(CONFIG_MESON_G12A) += board-g12a.o
obj-$(CONFIG_MESON_A1) += board-a1.o
+obj-$(CONFIG_MESON_T7) += board-t7.o
diff --git a/arch/arm/mach-meson/board-t7.c b/arch/arm/mach-meson/board-t7.c
new file mode 100644
index 00000000000..a6ccec25c0e
--- /dev/null
+++ b/arch/arm/mach-meson/board-t7.c
@@ -0,0 +1,97 @@
+// SPDX-License-Identifier: GPL-2.0+
+/*
+ * (C) Copyright 2026 Lucas Tanure <tanure@linux.com>
+ */
+
+#include <init.h>
+#include <asm/arch/boot.h>
+#include <asm/arch/mem.h>
+#include <asm/armv8/mmu.h>
+#include <asm/global_data.h>
+#include <asm/io.h>
+#include <linux/bitops.h>
+#include <linux/compiler.h>
+#include <linux/errno.h>
+#include <linux/kernel.h>
+
+DECLARE_GLOBAL_DATA_PTR;
+
+#define T7_WDT_CTRL 0xfe002100
+#define T7_WDT_CTRL_EN BIT(18)
+
+int board_init(void)
+{
+ /*
+ * The secure firmware boots BL33 with the watchdog running,
+ * disable it.
+ */
+ writel(readl(T7_WDT_CTRL) & ~T7_WDT_CTRL_EN, T7_WDT_CTRL);
+
+ return 0;
+}
+
+/*
+ * The secure world owns 0x05000000 - 0x09000000: it contains the BL31
+ * and BL32 runtime zones (also described as reserved-memory in the
+ * upstream devicetree) and further firmware-protected pages, and is
+ * left unmapped in t7_mem_map below. Reserve the whole span so nothing
+ * (EFI allocations, boot-time relocations) is ever placed in memory
+ * U-Boot cannot access.
+ */
+#define T7_SECMON_RSVMEM_START 0x05000000UL
+#define T7_SECMON_RSVMEM_SIZE 0x04000000UL
+
+void meson_init_reserved_memory(__maybe_unused void *fdt)
+{
+ meson_board_add_reserved_memory(fdt, T7_SECMON_RSVMEM_START,
+ T7_SECMON_RSVMEM_SIZE);
+}
+
+int meson_get_boot_device(void)
+{
+ return -ENOSYS;
+}
+
+phys_size_t get_effective_memsize(void)
+{
+ /*
+ * The top 8 MiB of the first DRAM bank contain pages the secure
+ * world protects at runtime, keep U-Boot below them.
+ */
+ return min(gd->ram_size, (phys_size_t)0xdf800000);
+}
+
+static struct mm_region t7_mem_map[] = {
+ {
+ /* DRAM below the secure monitor reserved zone */
+ .virt = 0x00000000UL,
+ .phys = 0x00000000UL,
+ .size = 0x05100000UL,
+ .attrs = PTE_BLOCK_MEMTYPE(MT_NORMAL) |
+ PTE_BLOCK_INNER_SHARE
+ }, {
+ /*
+ * DRAM between the secure monitor reserved zone and the
+ * end of the first bank. 0x05100000 - 0x09000000 is
+ * protected by the secure world and must not be mapped.
+ */
+ .virt = 0x09000000UL,
+ .phys = 0x09000000UL,
+ .size = 0xd7000000UL,
+ .attrs = PTE_BLOCK_MEMTYPE(MT_NORMAL) |
+ PTE_BLOCK_INNER_SHARE
+ }, {
+ /* Peripherals, GIC, ... */
+ .virt = 0xe0000000UL,
+ .phys = 0xe0000000UL,
+ .size = 0x20000000UL,
+ .attrs = PTE_BLOCK_MEMTYPE(MT_DEVICE_NGNRNE) |
+ PTE_BLOCK_NON_SHARE |
+ PTE_BLOCK_PXN | PTE_BLOCK_UXN
+ }, {
+ /* List terminator */
+ 0,
+ }
+};
+
+struct mm_region *mem_map = t7_mem_map;
--
2.55.0
next prev parent reply other threads:[~2026-08-06 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 10:18 [PATCH 0/4] Add Amlogic T7 (A311D2) and Khadas VIM4 support Lucas Tanure
2026-08-06 10:18 ` [PATCH 1/4] serial: meson: add Amlogic S4 UART support Lucas Tanure
2026-08-10 14:01 ` Ferass El Hafidi
2026-08-06 10:18 ` Lucas Tanure [this message]
2026-08-10 14:15 ` [PATCH 2/4] arm: meson: add Amlogic T7 SoC family support Ferass El Hafidi
2026-08-06 10:18 ` [PATCH 3/4] board: amlogic: add Khadas VIM4 support Lucas Tanure
2026-08-10 14:30 ` Ferass El Hafidi
2026-08-06 10:18 ` [PATCH 4/4] doc: board: amlogic: add Khadas VIM4 documentation Lucas Tanure
2026-08-10 8:13 ` [PATCH 0/4] Add Amlogic T7 (A311D2) and Khadas VIM4 support neil.armstrong
2026-08-10 14:12 ` Ferass El Hafidi
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=20260806101809.72526-3-tanure@linux.com \
--to=tanure@linux.com \
--cc=funderscore@postmasteros.org \
--cc=ilias.apalodimas@linaro.org \
--cc=neil.armstrong@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot-amlogic@groups.io \
--cc=u-boot@lists.u-boot-project.org \
/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.