u-boot.git/configs, branch v2026.07

drivers: sysreset: revert support for args in request

2026-07-03T19:45:58Z

This reverts: - commit e49c84f7bb7b ("doc: usage: cmd: reset: specify when the -edl option is available") - commit 1076feb8a3f9 ("cmd: boot: fix edl being shown when not supported") - commit 63c806ba0e12 ("qcom_defconfig: enable psci based sysreset") - commit ef06c5d76ff4 ("cmd: boot: Add '-edl' option to reset command documentation") - commit 32825eaddc37 ("sysreset: Implement PSCI based reset to EDL mode for QCOM SoCs") - commit fcb48b89813b ("drivers: sysreset: Add sysreset op that can take arguments") There was a conflict reverting commit 63c806ba0e12 ("qcom_defconfig: enable psci based sysreset") due to commit 02ef1859b44f ("configs: Resync with savedefconfig"), but the conflict resolution was trivial. The args support for the sysreset uclass contains a logic bug. The first sysreset device implementing the request_arg callback will consume the args, not support the specified arg and thus return -EPROTONOSUPPORT which will stop the iteration over all sysreset devices. This is an issue if one has multiple sysreset devices and each with support for different (valid) args. If a sysreset device implements a -dummy argument and another -foo and a user calls reset -dummy from the U-Boot CLI, it'll depend on which sysreset device will be attempted first. If it is the one implementing -foo, it'll return it doesn't support the argument with -EPROTONOSUPPORT in which case the device implementing -dummy will never be attempted and instead we'll do a cold reset which is very likely not what's expected from the user. Casey suggested[1] we revert this and start from scratch again with a different implementation instead. [1] https://lore.kernel.org/u-boot/77ff0f56-5c3b-42e7-bdd1-bf90296da900@linaro.org/ Acked-by: Casey Connolly Signed-off-by: Quentin Schulz

configs: phycore_am62x_a53_defconfig: Enable fastboot

2026-06-17T19:55:15Z

Enable USB fastboot support for downloading and flashing images via the fastboot protocol. Signed-off-by: Wadim Egorov

arm: dts: renesas: Enable DBSC5 on R-Car R8A78000 X5H Cortex-M33 RSIP port

2026-06-16T03:38:25Z

Bind the DBSC5 DRAM controller driver on boot in board_early_init_r(), which brings up the DBSC5 DRAM controller and its PHY and which enables access to DRAM present on this system. Add default boot command which loads additional bootloader components from HF and UFS storage into SRAM and DRAM, and starts those components on SCP and AP core 0. The system is then capable of reaching U-Boot on the AP core 0. Specifically, the following components are loaded: - SCP firmware, 384 kiB from HF offset 0x4c0000 to SCP STCM - TFA BL31, 256 kiB from UFS0 offset 0x5000 * 4 kiB sectors to DRAM 0x8c200000 - TEE, 2 MiB from UFS0 offset 0x5200 * 4 kiB sectors to DRAM 0x8c400000 - U-Boot, 1 MiB from UFS0 offset 0x7200 * 4 kiB sectors to DRAM 0x8c300000 - IPL parameters table is generated at DRAM address 0x8c100000 Enable pstore command support to allow dumping kernel console from pstore/ramoops, which is convenient for debugging. Use as follows: => pstore set 0x80000000 0x10000 0x400 0x8000 0 0 0 => pstore display console Signed-off-by: Marek Vasut

configs: verdin-imx95: enable PCI_INIT_R

2026-06-12T14:45:28Z

Currently, the ENETC device on iMX95 is not enumerated before network initialization because pci_init() is not called. As a result, no Ethernet device is registered. Enable CONFIG_PCI_INIT_R so the PCI buses are enumerated early enough for the Ethernet Controller to be detected and used. Fixes: 60d8255d8dc0 ("board: toradex: add Toradex Verdin iMX95") Signed-off-by: Franz Schnyder Reviewed-by: Francesco Dolcini

configs: toradex-smarc-imx95: enable PCI_INIT_R

2026-06-12T14:45:28Z

Currently, the ENETC device on iMX95 is not enumerated before network initialization because pci_init() is not called. As a result, no Ethernet device is registered. Enable CONFIG_PCI_INIT_R so the PCI buses are enumerated early enough for the Ethernet Controller to be detected and used. Fixes: ff0540fcfe49 ("board: toradex: add Toradex SMARC iMX95") Signed-off-by: Franz Schnyder Reviewed-by: Francesco Dolcini

Merge tag 'u-boot-rockchip-20260610' of https://source.denx.de/u-boot/custodians/u-boot-rockchip

2026-06-10T19:12:35Z

CI: https://source.denx.de/u-boot/custodians/u-boot-rockchip/-/pipelines/30398 Please pull the updates for rockchip platform: - New Board support: rk3588 FriendlyElec NanoPi R76S - UFS boot from SPL for rk3576 (NanoPi M5, ROCK 4D) - Clock support for RK3576 GMAC 25MHz output and RK3528/RK3576 USB3 OTG - Switch rk3128/rk3229 boards to upstream devicetree - MAINTAINERS update for upstream devicetree references - rk3588-rock-5b: Remove USB-C controller from u-boot.dtsi

configs: qcs615/qcs9100: Enable watchdog autostart

2026-06-10T11:36:18Z

Enable watchdog autostart for QCS615 and QCS9100 platforms to ensure the watchdog timer is automatically started during U-Boot initialization. Signed-off-by: Balaji Selvanathan Link: https://patch.msgid.link/20260526-wdt-v1-1-8236040fe56a@oss.qualcomm.com Signed-off-by: Casey Connolly

rockchip: Switch rk3229 boards to upstream devicetree

2026-06-08T13:34:59Z

Switch rk3229 boards to upstream devicetree. Signed-off-by: Johan Jonker Reviewed-by: Kever Yang

rockchip: Switch rk3128 boards to upstream devicetree

2026-06-08T13:34:59Z

Switch rk3128 boards to upstream devicetree. Signed-off-by: Johan Jonker Reviewed-by: Kever Yang

rockchip: rk3576-nanopi-m5: Enable UFS support

2026-06-08T13:32:40Z

NanoPi M5 supports UFS modules to be inserted into its eMMC/UFS slot, using the on-chip UFS controller inside the RK3576 SoC. Enable respective drivers in its default config to be able to load kernels from UFS. Signed-off-by: Alexey Charkov Reviewed-by: Kever Yang