u-boot/u-boot.git, branch next

Merge tag 'fsl-qoriq-next-2026-07-06' of https://source.denx.de/u-boot/custodians/u-boot-fsl-qoriq into next

2026-07-06T18:00:26+00:00

CI: https://source.denx.de/u-boot/custodians/u-boot-fsl-qoriq/-/pipelines/30622 - ls1028ardb: Move environment variables from header to .env file - crypto: fsl: Hide CAAM_64BIT symbol behind FSL_CAAM dependency - gpio: mpc8xxx: Add set_flags/get_flags ops - power: domain: scmi: Allow failure in getting power domain attribute

power: domain: scmi: Allow failure in getting power domain attribute

2026-07-06T02:24:46+00:00

When one power domain fails to get attribute, continue getting attribute for remaining power domains, not return probe failure. So other power domains are still functional. It is possible that one power domain is assigned to other agent or this power domain is disabled by HW fuse, so platform returns denied or other error. Signed-off-by: Ye Li Reviewed-by: Peng Fan Signed-off-by: Peng Fan

crypto: fsl: Hide CAAM_64BIT symbol behind FSL_CAAM

2026-07-06T02:20:34+00:00

Make CAAM_64BIT selectable only in case FSL_CAAM is selected, otherwise CAAM_64BIT shows up in configs of unrelated platforms. Signed-off-by: Marek Vasut Reviewed-by: Tom Rini Reviewed-by: Peng Fan Reviewed-by: Heiko Schocher Signed-off-by: Peng Fan

gpio: mpc8xxx: add set_flags/get_flags ops

2026-07-06T01:59:58+00:00

mpc8xxx_gpio_open_drain_on() / _off() helpers can program GPODR (open-drain enable) on QorIQ silicon, but they are not called. The open-drain capability is therefore unreachable from the GPIO uclass. Adding a set_flags op for the GPIOD_OPEN_DRAIN, plus a get_flags for the reports of state by reading GPDIR and GPODR back. For existing callers, it is unchanged: direction_input, direction_output, get_value, set_value and get_function still drive the same registers as before. The new ops only become observable when a caller explicitly asks for the GPIOD_OPEN_DRAIN flag (or queries flags via the uclass). Signed-off-by: Vincent Jardin Signed-off-by: Peng Fan

ls1028ardb: Move environment variables to .env file

2026-07-06T01:58:58+00:00

Move the bulk of the board environment from CFG_EXTRA_ENV_SETTINGS in ls1028ardb.h to board/nxp/ls1028a/ls1028ardb.env. Because the board directory is shared with ls1028aqds, the file is selected through CONFIG_ENV_SOURCE_FILE rather than the SYS_BOARD default. The distro_bootcmd machinery cannot be expressed in a .env file. The BOOTENV macro expands to environment text with embedded NUL separators, and the board overrides three distro variables (boot_scripts, boot_a_script and scan_dev_for_boot_part) that must follow BOOTENV to take effect. BOOTENV and those three overrides therefore remain in CFG_EXTRA_ENV_SETTINGS, which is concatenated after the .env text, while every other variable moves to the .env file. The resulting default environment is functionally unchanged for both the ls1028ardb_tfa and ls1028ardb_tfa_SECURE_BOOT defconfigs. This was verified with an order aware comparison of the default environment before and after the change. The only difference is that three accidental double spaces in xspi_bootcmd, sd_bootcmd and emmc_bootcmd collapse to single spaces, because the preprocessor normalises whitespace in the now unquoted text, which does not affect command parsing. Signed-off-by: Aristo Chen Signed-off-by: Peng Fan

Merge patch series "bootdev: few fixes for automatic boot"

2026-07-03T16:14:32+00:00

dmukhin@ford.com says: This series addresses few findings in bootdev code. Patch 1 fix for automatic boots in case higher-priority bootdevs fail to be hunted. Patch 2 adds unit test for patch 1. Link: https://lore.kernel.org/r/20260623220630.2828767-1-dmukhin@ford.com

test: bootdev: scan with a broken high-priority device

2026-07-03T16:14:25+00:00

Add bootdev_hunt_fallthrough() test to verify that 'bootflow scan -l' falls back to a lower-priority bootdev when a higher-priority hunter fails. Introduce a simple 'sandbox-bootdev' device for the test. The new bootdev can be configured to produce an error at the hunting stage. Introduce new host_set_flags_by_label() API and a flags field to 'host_sb_plat' to simulate a bootdev hunter failure for the test. Adjust boot{dev,flow} tests which depend on bootdev hunters. Signed-off-by: Denis Mukhin Reviewed-by: Simon Glass

bootdev: scan boot devices at each priority level

2026-07-03T16:14:25+00:00

Currently, default 'bootflow scan -lb' will stop booting the board if any of higher-priority bootdevs fail to be hunted even if there are bootdevs of lower priority. For example, if the board has both NVMe (priority 4) and USB MSD devices (priority 5), and if NVMe bootdev hunt fails (in the event of a bad NVMe firmware update), USB (which may be a recovery bootdev) is never hunted automatically, leaving the board at the U-Boot prompt (user intervention is needed, e.g. something like 'bootflow scan usb' to hunt USB). Fix bootdev_next_prio() to scan bootdevs at the lower priority level by not exiting the scan loop early. Keep the existing logging verbosity unchanged and rely on the failing subsystem to provide a suitable diagnostic message. Signed-off-by: Denis Mukhin Reviewed-by: Simon Glass

Merge patch series "bootm: fix flush_cache() with IH_TYPE_KERNEL_NOLOAD"

2026-07-03T16:13:14+00:00

This patch series from Nora Schiffer addresses a few issues with correctly handling IH_TYPE_KERNEL_NOLOAD in a few cases. Link: https://lore.kernel.org/r/20260622111933.1488593-1-nora.schiffer@ew.tq-group.com

bootm: allow omitting entry point for IH_TYPE_KERNEL_NOLOAD

2026-07-03T16:11:11+00:00

For IH_TYPE_KERNEL_NOLOAD, the entry point is given relative to the image start, making 0 a valid default, and for IH_OS_EFI, it is ignored altogether, so it may be preferable to omit it. Signed-off-by: Nora Schiffer Reviewed-by: Simon Glass