From: Pali Rohár <pali@kernel.org>
Date: Fri, 9 Sep 2022 15:32:38 +0000 (+0200)
Subject: common/memsize.c: Fix get_effective_memsize() to always check for CONFIG_MAX_MEM_MAPPED
X-Git-Tag: v2023.07~312^2~6^2~11
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=7210e457d5d166b4409bde402fd95a99e87cdfc5;p=platform%2Fkernel%2Fu-boot.git

common/memsize.c: Fix get_effective_memsize() to always check for CONFIG_MAX_MEM_MAPPED

CONFIG_MAX_MEM_MAPPED when defined specifies upper memory mapped limit.
So check for it always, and not only when CONFIG_VERY_BIG_RAM is defined.

Signed-off-by: Pali Rohár <pali@kernel.org>
---

diff --git a/common/memsize.c b/common/memsize.c
index d5d13d5..31884ac 100644
--- a/common/memsize.c
+++ b/common/memsize.c
@@ -94,7 +94,7 @@ long get_ram_size(long *base, long maxsize)
 
 phys_size_t __weak get_effective_memsize(void)
 {
-#ifndef CONFIG_VERY_BIG_RAM
+#ifndef CONFIG_MAX_MEM_MAPPED
 	return gd->ram_size;
 #else
 	/* limit stack to what we can reasonable map */