u-boot.git/board, branch v2025.07

mailmap: Update email for Duje Mihanović

2025-06-26T20:22:39Z

I'm moving to a new address, so map my old one to it. Also update the MAINTAINERS entries. Signed-off-by: Duje Mihanović

board: samsung: e850-96: Load LDFW in board_late_init()

2025-06-22T16:16:23Z

As stated in 5e847f7729b3 ("efi_loader: call efi_init_early() earlier"): efi_init_early() creates an event hook for block device probing. It has to be called before any block device is probed. Indeed, efi_bl_init() registers EVT_DM_POST_PROBE event, which calls efi_disk_probe() whenever any block device is probed. And to make that hook work, the initialization of all block devices was put after efi_init_early() in initcall_run_r(): INITCALL(efi_init_early); INITCALL(initr_nand); INITCALL(initr_onenand); INITCALL(initr_mmc); Because LDFW firmware is being read from MMC, attempt to load LDFW in board_init() causes MMC driver to be probed. And because board_init() is executed before efi_init_early(), the hook mentioned above won't work for MMC devices anymore. So EFI disk objects won't be created, which in turn makes the EFI subsystem non-functional, showing next symptoms: - 'efidebug dh' output is empty - attempt to add boot devices in 'eficonfig' shows this message: "No block device found!" - 'bootefi selftest $fdtcontroladdr' shows this warning: "Cannot persist EFI variables without system partition" - booting GRUB with 'bootefi' runs minimal GRUB shell which doesn't see any block devices as well, probably because EFI vars weren't passed Load LDFW in board_late_init() instead, as it's called after efi_init_early(). This fixes the described problem and makes it possible to run EFI apps like GRUB correctly, add entries in 'eficonfig', and makes 'efivar --list' command in Linux rootfs actually show EFI variables. The only user of LDFW at the moment is the TRNG driver, and it's probed later, only when it's going to be used (e.g. on "rng" command). So it's fine to load LDFW in board_late_init(). Now the corresponding call order will look like this: efi_init_early() initr_mmc() mmc_probe() EVT_DM_POST_PROBE -> efi_disk_probe() board_late_init() load_ldfw() -> fs_read(), blk_dread() exynos_trng_probe() Fixes: ccfd8de541a8 ("board: samsung: e850-96: Report LDFW loading failures") Fixes: f04e58cc9788 ("board: samsung: e850-96: Load LDFW firmware on board init") Signed-off-by: Sam Protsenko

arm: kirkwood: Maintainer for RaidSonic ICY BOX ib62x0 board

2025-06-21T16:55:48Z

Add me as maintainer for the RaidSonic ICY BOX ib62x0. Signed-off-by: Tony Dinh

arm64: dts: renesas: r8a779g3: Add Retronix R-Car V4H Sparrow Hawk board support

2025-06-10T18:50:50Z

Add Retronix R-Car V4H Sparrow Hawk board based on Renesas R-Car V4H ES3.0 (R8A779G3) SoC. This is a single-board computer with single gigabit ethernet, DSI-to-eDP bridge, DSI and two CSI2 interfaces, audio codec, two CANFD ports, micro SD card slot, USB PD supply, USB 3.0 ports, M.2 Key-M slot for NVMe SSD, debug UART and JTAG. DT is imported from Linux next commit: a719915e76f2 ("arm64: dts: renesas: r8a779g3: Add Retronix R-Car V4H Sparrow Hawk board support") Signed-off-by: Marek Vasut

arm64: renesas: Introduce renesas_dram_init_banksize()

2025-06-10T18:50:50Z

Introduce weak renesas_dram_init_banksize() function which is meant to be used to adjust DRAM bank sizes after the common Renesas board DRAM bank handling code finished. This is mainly meant for boards which ship with multiple DRAM size options, which can be detected at runtime. This allows such boards to ship with single U-Boot binary on all boards. Signed-off-by: Marek Vasut

board: ti: am62ax: env: Use default MMC related args

2025-06-04T17:58:11Z

There are common MMC args for TI plats in include/environment/ti/mmc.env. Since we already include this, there is no need to redefine these MMC vars. Use the defaults. This seems like something that could have been done while refactoring these vars in the first place as it happened after this AM62A file was available hence the fixes tag. Reported-by: Chirag Shilwant Fixes: 3709b529156e ("env: ti: mmc.env: Move mmc related args to common place") Signed-off-by: Andrew Davis Reviewed-by: Neha Malcom Francis Acked-by: Chirag Shilwant Reviewed-by: Judith Mendez

board: dragonboard410c: Fix button cmd name

2025-06-02T16:19:27Z

Commit 359e1d4a57e0 ("board: dragonboard410c: Use button_cmd instead of custom code") was made in parallel with commit 8f5685d5d32f ("button: qcom-pmic: prettify and standardise button labels"), which changed the default button label from "vol_down" to "Volume Down". This is causing errors in the console during boot now: No button labelled 'vol_down' Fix this by using the new label. Fixes: 359e1d4a57e0 ("board: dragonboard410c: Use button_cmd instead of custom code") Fixes: 8f5685d5d32f ("button: qcom-pmic: prettify and standardise button labels") Signed-off-by: Stephan Gerhold Reviewed-by: Reviewed-by: Sumit Garg Link: https://lore.kernel.org/r/20250417-db410c-fixes2-v1-1-76ad994da152@linaro.org Signed-off-by: Casey Connolly

board: rzg2l: Update MAINTAINERS file

2025-05-28T22:53:43Z

Un-orphan the RZ/G2L , keep the RZ/G2L maintained. Signed-off-by: Marek Vasut Reviewed-by: Paul Barker

board: rzg2l: Drop myself to reviewer for RZ/G2L boards

2025-05-28T22:53:43Z

I still intend to review patches, and will be using my own email address going forward. Signed-off-by: Paul Barker

x86: efi_loader: Ensure the SMBIOS tables are sent via EFI

2025-05-25T09:40:00Z

The EFI-loader code has not been fully converted to use bloblist, so relies on the SMBIOS-table address being set in global_data. Set this up in write_tables() so that the SMBIOS tables are actually available. Enable the command for x86 QEMU so that the SMBIOS tests actually run. Signed-off-by: Simon Glass Fixes: 83ce35d6ebb ("emulation: Use bloblist to hold tables") Reported-by: Niklas Sombert Tested-by: Niklas Sombert Tested-by: Heinrich Schuchardt Reviewed-by: Heinrich Schuchardt