u-boot.git/drivers, branch main

Merge patch series "dm: core: misc fixes"

2026-07-16T18:03:23Z

Peng Fan (OSS) says: A few misc fixes to dm core. More information could be found in each commit. Patch list: dm: core: free old name in device_set_name to prevent leak dm: core: Correct calloc arguments dm: core: fix wrong strlen check in of_add_subnode dm: core: free fdt when fdt_create_empty_tree failure Link: https://lore.kernel.org/r/20260703-dm-core-v1-0-076d395bded4@nxp.com

dm: core: free old name in device_set_name to prevent leak

2026-07-16T18:03:05Z

If device_set_name is called on a device that already has DM_FLAG_NAME_ALLOCED set, the old dynamically-allocated name is leaked. Free it before assigning the new name. See: drivers/net/mdio_gpio.c:mdio_gpio_bind(). There is device_set_name() here, however dm_mdio_post_bind() will also call device_set_name() if "device-name" exists. Signed-off-by: Peng Fan Reviewed-by: Simon Glass

dm: core: Correct calloc arguments

2026-07-16T18:03:05Z

Every other calloc in drivers/core uses calloc(count, size) with count first. Fix the two reversed calloc(sizeof, 1) calls for consistency. Signed-off-by: Peng Fan Reviewed-by: Raphaël Gallais-Pou Reviewed-by: Simon Glass

dm: core: fix wrong strlen check in of_add_subnode

2026-07-16T18:03:05Z

The duplicate-name check uses strlen on the search name instead of the child name, so a child named "trevor" would falsely match a search for "trev". Fix by checking strlen of child->name. Signed-off-by: Peng Fan Reviewed-by: Raphaël Gallais-Pou Reviewed-by: Simon Glass

dm: core: free fdt when fdt_create_empty_tree failure

2026-07-16T18:03:05Z

If fdt_create_empty_tree fails, the malloc-ed fdt buffer is never freed. Add free before the error return. Signed-off-by: Peng Fan Reviewed-by: Raphaël Gallais-Pou Reviewed-by: Simon Glass

Merge tag 'efi-2026-10-rc1' of https://git.u-boot-project.org/u-boot/custodians/u-boot-efi

2026-07-16T14:10:11Z

Pull request efi-2026-10-rc1 CI: https://git.u-boot-project.org/u-boot/custodians/u-boot-efi/-/pipelines/648 Documentation: * board: renesas: Document SH/Aarch32/Aarch64 toolchain setup * board: renesas: Document Aarch32 toolchain setup in RZ/N1 * board: renesas: Document Renesas R-Car Gen3 H3/M3-W/M3-N Salvator-X(S) board * board: renesas: Document Renesas R-Car Gen3 H3/M3-W/M3-N ULCB board * board: renesas: Document Renesas R-Car Gen3 M3Le Geist board * board: renesas: Document Renesas R-Car Gen3 E3 Ebisu board * board: renesas: Document Renesas R-Car Gen3 D3 Draak board * board: renesas: Document Retronix R-Car Gen4 V4H Sparrow Hawk board * board: renesas: Document Renesas R-Car Gen5 X5H Ironhide board * board: renesas: Update Renesas generic build section * board: renesas: Convert Renesas board support table to grid table * boards: amlogic: update documentation for Beelink GT1 Ultimate * CONTRIBUTE: use internal link instead of hardcoded external URL * CONTRIBUTE: tell people reviewing *is* contributing * CONTRIBUTE: explicitly list tests and documentation as welcome contributions UEFI: * fix building with CONFIG_EFI_VARIABLES_PRESEED=y * fix buffer overrun in efi_sigstore_parse_siglist * Correctly count the size on DTB measurements * Change the return values if a TPM is missing during GetEventLog * Measure secure boot variables in the correct PCR if DeployedMode is set * fix missing EFI_EXIT in efi_disconnect_controller * efi_selftest: free handles on teardown() * efi_selftest: test block io revision and pointers Others: * qfw: fix RSDP ACPI table ext_checksum computation

qfw: fix RSDP ext_checksum recomputation

2026-07-15T22:40:42Z

table_compute_checksum() returns the value that makes the byte sum of the buffer zero. If the ext_checksum field already contains a non-zero value (as QEMU's firmware-provided RSDP does), adding that existing value into the sum produces an incorrect complement. Zero the field before calling table_compute_checksum() so the calculation starts from a clean state, matching the pattern used in acpi_write_rsdp(). Reviewed-by: Simon Glass Reviewed-by: Ilias Apalodimas Signed-off-by: Heinrich Schuchardt

clk: ti: Use CPU ticks to count timeout

2026-07-15T19:53:46Z

readl_relaxed_poll_timeout() relies on timers. On the beaglebone black, the timer used by readl_relaxed_poll_timeout() depends on this clock driver. So we have a sort of circular dependency [enable_clock -> timer_init -> enable_clock -> timer_init]. It leads to a division-per-zero during the second timer_init() and the beaglebone fails to boot with following message: | CPU : AM335X-GP rev 2.1 | Model: TI AM335x BeagleBone Black | DRAM: 512 MiB | ### ERROR ### Please RESET the board ### Replace readl_relaxed_poll_timeout() with a simple loop that uses CPU ticks to countdown the timeout. This loop and the value of LDELAY are inspired from what's done in arch/arm/mach-omap2/am33xx/clock.c Also, arch/arm/mach-omap2/am33xx/clock.c doesn't return an error on timeout, it only logs it, so let's stick with it. Fixes: de2e3f00f2fa ("clk: ti: Remove AM33xx dependency") Signed-off-by: Bastien Curutchet Reported-by: Tom Rini Tested-by: Tom Rini

Merge patch series "pinctrl: aspeed: Add AST2700 pinctrl drivers"

2026-07-14T21:41:13Z

Billy Tsai says: The AST2700 is Aspeed's 7th-generation BMC SoC with a dual-die architecture: SoC0 (CPU die) and SoC1 (I/O die) each have their own SCU with independent multi-function pin controls. Initial AST2700 platform support is already merged in next, including the ast2700.dtsi pinctrl0 and pinctrl1 nodes, but no pinctrl driver backs them yet. This series adds one pinctrl driver per die, each followed by a patch adding its pin configuration support. Both drivers use the generic pinctrl framework and are compatible with the Linux kernel device tree bindings, using the same group and function names as the Linux aspeed,ast2700-soc0/soc1-pinctrl drivers so pin states can be shared between the kernel and U-Boot device trees. Patch 1 adds the SoC0 driver, which models each (function, group) pair as a flat register mask/value table covering eMMC, VB, VGA DDC, JTAG master port select, PCIe RC PERST and USB2/USB3 port routing. Patch 2 adds SoC0 pin configuration support: every GPIO18A/GPIO18B ball has its own IO control register providing a 3 mA to 41 mA drive strength selector and bias control. Patch 3 adds the SoC1 driver, porting the per-pin 4-bit multi-function selector scheme (220 pins, 238 groups, 217 functions) together with the virtual pins for PCIe RC2 PERST, the USB2 port C/D mode and SGMII controls. Patch 4 adds SoC1 pin configuration support: a per-pin bias enable bit and sparse 2-bit drive strength fields (4 mA to 16 mA in 4 mA steps) mirroring the Linux driver layout. The bias-disable, bias-pull-down, bias-pull-up and drive-strength properties can be applied per pin or per group. Both drivers implement gpio_request_enable so the GPIO driver can reclaim pins through the gpio-ranges already present in ast2700.dtsi, and provide get_pin_muxing so "pinmux status" reports the active signal of every pin. Link: https://lore.kernel.org/r/20260702-pinctrl-v1-0-4d2bd89fc213@aspeedtech.com

pinctrl: aspeed: Add AST2700 SoC1 pinconf support

2026-07-14T21:40:20Z

The SoC1 SCU provides a bias enable bit per pin in the registers at 0x480 (setting the bit disables the bias; the pull direction is fixed in silicon) and 2-bit drive strength fields at 0x4C0 selecting 4 mA to 16 mA in 4 mA steps. The pin-to-field mapping of the drive strength registers is sparse and non-linear, so it is kept in a lookup table mirroring the Linux driver; pins without an entry reject drive-strength with -ENOTSUPP. Support the bias-disable, bias-pull-down, bias-pull-up and drive-strength properties per pin and per group, and select PINCONF so the generic pinctrl framework parses them. Signed-off-by: Billy Tsai