u-boot.git/arch/arm/mach-mediatek, branch next

arm: mediatek: use phase-aware PSCI reset on MT8195

2026-08-13T16:36:04Z

Change IS_ENABLED() to CONFIG_IS_ENABLED() to prepare for SPL support. PSCI is not available in the SPL stage and would cause a lock-up if called. Reviewed-by: Julien Stephan Link: https://patch.msgid.link/20260731-mtk-mach-phase-aware-reset-v1-2-90b918aa52f5@baylibre.com Signed-off-by: David Lechner

arm: mediatek: use phase-aware PSCI reset on MT8365

2026-08-13T16:36:04Z

Change IS_ENABLED() to CONFIG_IS_ENABLED() to prepare for SPL support. PSCI is not available in the SPL stage and would cause a lock-up if called. Reviewed-by: Julien Stephan Link: https://patch.msgid.link/20260731-mtk-mach-phase-aware-reset-v1-1-90b918aa52f5@baylibre.com Signed-off-by: David Lechner

arm: mediatek: use phase-aware PSCI reset on MT8188

2026-08-05T20:05:32Z

MT8188 reset_cpu() checks the U-Boot proper PSCI symbol even when the function is built for SPL. A standalone SPL download agent runs before BL31, so fastboot acknowledges a reboot request and then stalls while attempting an unavailable PSCI system reset. Use the phase-aware configuration check so SPL falls back to the watchdog reset provider. U-Boot proper continues to use PSCI as before. Signed-off-by: Carlo Caione Reviewed-by: Julien Stephan Link: https://patch.msgid.link/20260724-ccaione-upstream-mt8188-spl-reset-v1-1-08da6554ecd8@baylibre.com Signed-off-by: David Lechner

clk: mediatek: mt8516: unique driver names

2026-07-22T17:41:03Z

Change driver names for MediaTek mt8516 clocks to be globally unique. This will allow better build bot testing by allowing all clocks to be compiled at the same time. Link: https://patch.msgid.link/20260707-mtk-clk-unique-driver-names-v1-14-283d9a55361e@baylibre.com Signed-off-by: David Lechner

clk: mediatek: mt7629: unique driver names

2026-07-22T17:41:03Z

Change driver names for MediaTek mt7629 clocks to be globally unique. This will allow better build bot testing by allowing all clocks to be compiled at the same time. Link: https://patch.msgid.link/20260707-mtk-clk-unique-driver-names-v1-3-283d9a55361e@baylibre.com Signed-off-by: David Lechner

Merge branch 'next'

2026-07-07T00:26:12Z

Kconfig: arm: restyle

2026-06-25T20:06:18Z

Restyle all Kconfigs for "arm": Menu entries : no space left Menu attributes: 1 TAB Help text : 1 TAB + 2 spaces Replace '---help---' by 'help' Signed-off-by: Johan Jonker Reviewed-by: Tom Rini

arm: mediatek: mt8512: fix gd->bd->bi_dram[0].size

2026-06-24T15:06:16Z

Use board_get_usable_ram_top() instead of get_effective_memsize() to limit gd->ram_top. Both board_get_usable_ram_top() and get_effective_memsize() are used to set gd->ram_top in setup_dest_addr(). However, get_effective_memsize() also sets gd->bd->bi_dram[0].size in dram_init_banksize(), which is undesirable. Prior to commit b9e6281632a8 ("arm: mediatek: mt8512: drop dram_init_banksize()"), gd->bd->bi_dram[0].size was overridden in a board-specific dram_init_banksize() implementation. We can just use board_get_usable_ram_top() now to set gd->ram_top to the correct value instead. Overriding gd->bd->bi_dram[0].size was a bit confusing since it isn't easily apparent which order the functions that set it are called. Fixes: b9e6281632a8 ("arm: mediatek: mt8512: drop dram_init_banksize()") Link: https://patch.msgid.link/20260615-mtk-fix-ram-size-v2-8-f72cfc52ce58@baylibre.com Signed-off-by: David Lechner

arm: mediatek: mt8195: fix gd->bd->bi_dram[0].size

2026-06-24T15:06:16Z

Use board_get_usable_ram_top() instead of get_effective_memsize() to set gd->ram_top to something <= 4GiB. Both board_get_usable_ram_top() and get_effective_memsize() are used to set gd->ram_top in setup_dest_addr(). However, get_effective_memsize() also sets gd->bd->bi_dram[0].size in dram_init_banksize(), which is undesirable. Prior to commit d83bd9729d75 ("arm: mediatek: mt8195: drop dram_init_banksize()"), gd->bd->bi_dram[0].size was overridden in a board-specific dram_init_banksize() implementation. When that was removed get_effective_memsize() set gd->bd->bi_dram[0].size to the wrong value because of get_effective_memsize() being overridden in commit af4cba9a05aa ("arm: mediatek: mt8195: fix gd->ram_top limit") We can just use board_get_usable_ram_top() now to set gd->ram_top to the correct value instead. This is possible now, thanks to LMB_LIMIT_DMA_BELOW_RAM_TOP being set by default for 64-bit Mediatek ARM SoCs. Fixes: d83bd9729d75 ("arm: mediatek: mt8195: drop dram_init_banksize()") Link: https://patch.msgid.link/20260615-mtk-fix-ram-size-v2-7-f72cfc52ce58@baylibre.com Signed-off-by: David Lechner

arm: mediatek: mt8189: fix gd->bd->bi_dram[0].size

2026-06-24T15:06:16Z