summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarek Vasut <[email protected]>2026-06-04 19:33:15 +0200
committerTom Rini <[email protected]>2026-06-08 13:28:49 -0600
commit3dd149ba17cd34724bc535d6de290de6e74e177f (patch)
treea906b296fc070461847f4b92f84625fcd9c9994d
parent75daa277941702bf58c88d65c0cb6ed962899d9e (diff)
lmb: Rename LMB_LIMIT_DMA_BELOW_4G to LMB_LIMIT_DMA_BELOW_RAM_TOP
Rename LMB_LIMIT_DMA_BELOW_4G to LMB_LIMIT_DMA_BELOW_RAM_TOP to make the Kconfig option more descriptive. No functional change. Suggested-by: Ilias Apalodimas <[email protected]> Signed-off-by: Marek Vasut <[email protected]> Reviewed-by: Ilias Apalodimas <[email protected]>
-rw-r--r--lib/Kconfig7
-rw-r--r--lib/lmb.c2
2 files changed, 5 insertions, 4 deletions
diff --git a/lib/Kconfig b/lib/Kconfig
index 29911068a69..cf13ac1bdad 100644
--- a/lib/Kconfig
+++ b/lib/Kconfig
@@ -1295,13 +1295,14 @@ config SPL_LMB_ARCH_MEM_MAP
memory map. Enable this config in such scenarios which allow
architectures and boards to define their own memory map.
-config LMB_LIMIT_DMA_BELOW_4G
+config LMB_LIMIT_DMA_BELOW_RAM_TOP
bool
depends on LMB
default y if ARCH_BCM283X
help
- Some architectures can not DMA above 4 GiB boundary,
- limit available memory to memory below 4 GiB boundary.
+ Some architectures can not DMA above ram_top boundary,
+ which is after 4 GiB or 32-bit boundary too. Limit the
+ available memory to memory below ram_top boundary.
config PHANDLE_CHECK_SEQ
bool "Enable phandle check while getting sequence number"
diff --git a/lib/lmb.c b/lib/lmb.c
index a2aeb526e29..275d105c5aa 100644
--- a/lib/lmb.c
+++ b/lib/lmb.c
@@ -628,7 +628,7 @@ static void lmb_add_memory(void)
if (size) {
lmb_add(bd->bi_dram[i].start, size);
- if (!IS_ENABLED(CONFIG_LMB_LIMIT_DMA_BELOW_4G))
+ if (!IS_ENABLED(CONFIG_LMB_LIMIT_DMA_BELOW_RAM_TOP))
continue;
bank_end = bd->bi_dram[i].start + size;