u-boot.git/include, branch next

Merge tag 'u-boot-rockchip-2027.01-20260828' of https://git.u-boot-project.org/u-boot/custodians/u-boot-rockchip into next

2026-08-29T15:56:00Z

- Fixed possible SPI hangs when only PICO is routed (TX-only), - Added support for ROC-RK3399-PC-PLUS (via roc-pc-rk3399_defconfig)

blkcache: include the hardware partition in the cache key

2026-08-26T20:51:31Z

The block cache keys its entries on (iftype, devnum, start, blkcnt, blksz) but not on the block descriptor's hardware partition. Devices that expose several independent address spaces through blk_desc->hwpart therefore alias each other in the cache: once a block has been cached for one hwpart, reads of the same LBA on another hwpart return the data cached for the first one. For MMC this is masked because switching hwpart invalidates the cache, but a UBI block device selects the target volume purely through hwpart and does not invalidate on switch, so scanning several UBI volumes returns the first volume's blocks for all of them. Add hwpart to the cache key so entries for different hardware partitions (or UBI volumes) are kept distinct. Fixes: e40cf34a29f1 ("drivers: block: add block device cache") Signed-off-by: Daniel Golle

tools: fit: sign all config image references

2026-08-25T23:12:40Z

Target-side configuration verification builds the signed-region list from every image-reference property in the selected configuration. Host-side signing still uses either the signature node sign-images property or the legacy kernel/fdt/script default list. This lets mkimage generate configuration signatures which U-Boot cannot verify when the configuration references other image types, such as firmware, loadables or ramdisk entries. It also lets the host and target disagree when sign-images names only a subset of the configuration images. Build the host-side signing list from the configuration properties in the same way as target-side verification. Use one shared property classifier so the host and target cannot drift apart again. This makes signed configurations cover the root node, the configuration node, every referenced image node, and its hash, cipher and dm-verity subnodes, regardless of image type. Warn when a legacy sign-images property is present, since it no longer limits the signed image list. Require every referenced image to have at least one hash subnode. Add sandbox coverage proving that a firmware reference omitted from sign-images is still recorded in hashed-nodes and verified. Update the signed-configuration documentation to describe the same rule and the hash-subnode requirement. Fixes: 2092322b31cc ("boot: Add fit_config_get_hash_list() to build signed node list") Signed-off-by: James Hilliard Reviewed-by: Simon Glass

Merge tag 'mediatek-for-next-2026-08-24' of https://git.u-boot-project.org/u-boot/custodians/u-boot-mediatek into next

2026-08-25T17:36:46Z

* New HDMI PHY and I2C DDC drivers, default EDID_ADDR macro * MT8189 clock qualifier fix * Phase-aware PSCI reset (MT8195/MT8365) * dwc_eth_qos MT8366 support * MediaTek TPHY v3 hardware support * mtk_snor mt8188/mt8189 compatible-string cleanup * MT6358/MT6366 PMIC regulator + pwrap support * MediaTek pinctrl Kconfig cleanup (per-SoC symbols → single driver + TARGET_*) * New MT8366 pinctrl driver + dt-bindings header * MediaTek serial driver clock-handling fixes

Merge tag 'v2026.10-rc3' into next

2026-08-25T01:31:25Z

dt-bindings: pinctrl: add MT8366 pin function header

2026-08-25T00:45:49Z

Add a header with MT8366 pin function definitions for use in devicetrees. Upstreaming of MT8366 has not even started yet, so we will have to carry a downstream version of this for some time. Signed-off-by: Deep Pani Link: https://patch.msgid.link/20260807-mtk-pinctrl-mt8366-v2-2-b7358bb31521@baylibre.com Signed-off-by: David Lechner

power: regulator: add MT6358 driver with MT6366 support

2026-08-24T23:17:38Z

Add a new driver for MediaTek MT6366 PMIC regulators. The register layout is compatible with MT6358, so the driver itself is called "mt6358". Only support for MT6366 is added currently for use with the MediaTek Genio 360 EVK. Reviewed-by: Julien Stephan Link: https://patch.msgid.link/20260807-mtk-pmic-mt6366-v2-1-d9fdef581fb1@baylibre.com Signed-off-by: David Lechner

lmb: Return -EFAULT when freeing unallocated memory regions

2026-08-24T19:58:00Z

Make lmb_free() return -EFAULT when the requested memory region is not allocated, instead of the generic -1 error value. Document the updated error code in the public API comment and change the LMB unit test to check for the new -EFAULT errno value. Signed-off-by: Jonas Karlman Reviewed-by: Randolph Sapp

lmb: Return -EFAULT when requested region is not part of memory map

2026-08-24T19:58:00Z

lmb_alloc_addr() is documented to return -EINVAL when the requested memory region is not part of the LMB memory map. However, -EINVAL is also used to e.g. indicate that a NULL pointer is passed as the addr parameter or when the requested memory region partially overlaps an existing region. Change lmb_alloc_addr() to return -EFAULT when the requested memory region is not part of the LMB memory map to make the type of error known to callers. Also extend unit tests to validate that the return code has stay the same when the requested memory region partially overlaps. No caller of lmb_alloc_addr() is checking what type of error code is returned, so this change has no intended behavior change. Signed-off-by: Jonas Karlman Reviewed-by: Randolph Sapp

spi: Handle spi-{tx, rx}-bus-width 0 as SPI_NO_TX/SPI_NO_RX

2026-08-24T08:53:00Z

The spi-peripheral-props binding shipped in dts/upstream allows a bus width of 0, meaning no RX or TX is possible on this device. The switches in spi_slave_of_to_plat() only handle 1/2/4/8, so a width of 0 falls through to the default case and warns "spi-rx-bus-width 0 not supported" on every boot, even though the devicetree is valid per the binding. The fact that the wire is missing is then dropped from plat->mode. Map 0 to new SPI_NO_TX/SPI_NO_RX mode bits, as Linux has done since v5.12 ("spi: Add SPI_NO_TX/RX support", mainline d962608ce218). Bits 16 and 17 are the first free mode bits. Mapping the bits is not enough on its own, as Quentin pointed out: nothing would stop a caller from asking for a transfer in a direction that has no wire, and every controller driver would need its own guard. Validate centrally in dm_spi_xfer() instead, matching Linux's __spi_validate(): a din on a SPI_NO_RX device or a dout on a SPI_NO_TX device fails with -EINVAL before it reaches the driver. A new sandbox test covers both rejections. This comes up on devices with no MISO line at all, such as a write-only SPI display described with spi-rx-bus-width = <0>. Signed-off-by: Cole Munz Acked-by: Quentin Schulz Link: https://patch.msgid.link/ae6a85d6f985b63c8f5a3fe8deeab89d79757b14.1787309754.git.Munzzyy1@proton.me Signed-off-by: Quentin Schulz