[PATCH] arm: mediatek: mt7988: restore full DRAM bank reporting

[rmandrad at gmail.com]

Not the header file as   TARGET_MT7988 sets SYS_CONFIG_NAME="mt7988" in arch/arm/mach-mediatek/Kconfig

In the mt7988 I don't see CFG_MAX_MEM_MAPPED used elsewhere than just in common/memsize.c where it limits get_effective_memsize() 

Unsetting/removing CFG_MAX_MEM_MAPPED would take u-boot above 4gb... Some MediaTek ARM64 ports may keep U-Boot below 4 GiB because peripherals such as MMC need DMA buffers below 4 GiB ... so, it may work on my setup but not others. Also, not an expert on u-boot  I would suggest for others to comment/review
 
-----Original Message-----
From: David Lechner <dlechner at baylibre.com> 
Sent: 05 June 2026 13:52
To: Rudy Andram <rmandrad at gmail.com>
Cc: u-boot at lists.denx.de; trini at konsulko.com; ryder.lee at mediatek.com; weijie.gao at mediatek.com; chunfeng.yun at mediatek.com; igor.belwon at mentallysanemainliners.org; jstephan at baylibre.com; GSS_MTK_Uboot_upstream at mediatek.com; emanuele.ghidoli at toradex.com
Subject: Re: [PATCH] arm: mediatek: mt7988: restore full DRAM bank reporting

On Tue, Jun 2, 2026 at 6:24 PM Rudy Andram <rmandrad at gmail.com> wrote:
>
> MT7988 detects the full installed DRAM in dram_init(), but after 
> commit bddd6bbef3dc ("arm: mediatek: mt7988: drop 
> dram_init_banksize()") it fell back to the generic dram_init_banksize() implementation.
>
> That generic path populates bd->bi_dram[0].size with 
> get_effective_memsize(), which is capped by CFG_MAX_MEM_MAPPED. On
> MT7988 this limits the exported DRAM bank to 3 GiB even when 8 GiB is 
> installed.

Can we just remove the #define CFG_MAX_MEM_MAPPED (and the header file that contains it)? Or is it used somewhere else?