summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2026-03-13net: do not use non-existent CONFIG_DM_CLKHeinrich Schuchardt
For enabling the clock driver we use symbol CONFIG_CLK. Select this symbol for the HiSilicon Fast Ethernet Controller driver. Signed-off-by: Heinrich Schuchardt <[email protected]> Reviewed-by: Quentin Schulz <[email protected]>
2026-03-13net: phy: air_en8811: add support for Airoha AN8811HB PHYTommy Shih
Add support for the Airoha AN8811HB 2.5 Gigabit PHY to the existing en8811h driver. This PHY supports 10/100/1000/2500 Mbps speeds. Update the driver to recognize the AN8811HB PHY ID and handle its specific firmware loading requirements. The firmware loading mechanism remains consistent with the existing implementation. This driver is based on: - Linux upstream PHY subsystem (v7.0-rc1) - air_an8811hb v0.0.4 out-of-tree uboot driver written by "Lucien.Jheng <[email protected]>" Tested on MT7987 RFB board. Link: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=6f1769ec5892ac41d82e820d94dcdc68e904aa99 Link: https://patchwork.kernel.org/project/netdevbpf/patch/[email protected]/ Signed-off-by: Tommy Shih <[email protected]> Reviewed-by: Lucien.Jheng <[email protected]>
2026-03-12Merge tag 'rpi-2026.04-rc4' of ↵Tom Rini
https://source.denx.de/u-boot/custodians/u-boot-raspberrypi Updates for RPi for 2026.04-rc4: - board/raspberrypi: add bcm2712d0-rpi-5-b for Raspberry Pi 5 - board/raspberrypi: add multi-FDT support - rpi: pass the Video Core logs DT parameter through - pinctrl: bcm283x: Fix GPIO pull state register values for BCM2711
2026-03-13riscv: mpfs: SIFIVE_CLINT and SPL_SIFIVE_CLINT don't existHeinrich Schuchardt
Don't imply non-existent symbols CONFIG_SIFIVE_CLINT and SPL_SIFIVE_CLINT. MPFS boards neither use SPL nor do they run main U-Boot in M-mode. So we don't need CONFIG_(SPL_)ACLINT either. Signed-off-by: Heinrich Schuchardt <[email protected]> Acked-by: Conor Dooley <[email protected]>
2026-03-13openpiton: imply CONFIG_SPL_CPUHeinrich Schuchardt
There is no symbol CONFIG_SPL_CPU_SUPPORT. The intended symbol is called CONFIG_SPL_CPU. Signed-off-by: Heinrich Schuchardt <[email protected]> Reviewed-by: Tianrui Wei <[email protected]> Fixes: 8a44fe694394 ("board: riscv: add openpiton-riscv64 SoC support") Reviewed-by: Quentin Schulz <[email protected]>
2026-03-13riscv: don't imply non-existent CONFIG_IP_DYNHeinrich Schuchardt
The symbol CONFIG_IP_DYN does not exist, but multiple contributors copied an imply statement. Remove the imply IP_DYN statements. Fixes: 3fda0262c33f ("riscv: Add SiFive FU540 board support") Fixes: 64413e1b7caf ("riscv: Add Microchip MPFS Icicle Kit support") Fixes: 70415e1e528d ("board: sifive: add HiFive Unmatched board support") Fixes: 6f902b85b6ee ("board: starfive: Add Kconfig for StarFive VisionFive v2 Board") Signed-off-by: Heinrich Schuchardt <[email protected]> Acked-by: Conor Dooley <[email protected]>
2026-03-13driver: cache: Remove SiFive PL2 driverNick Hu
Under single core boot platform, the secondary cores won't enter the u-boot spl. Therefore we move the pl2 driver from u-boot to the Opensbi. Signed-off-by: Nick Hu <[email protected]> Signed-off-by: Jimmy Ho <[email protected]> Reviewed-by: Leo Yu-Chi Liang <[email protected]>
2026-03-13sifive: switch to OF_UPSTREAMAndreas Schwab
Tested on HiFive Unleashed and HiFive Unmatched, both SPIFlash and MMC boot. Signed-off-by: Andreas Schwab <[email protected]> Reviewed-by: Leo Yu-Chi Liang <[email protected]>
2026-03-12boot: availability of command mii for NET_LWIPHeinrich Schuchardt
If we are using the legacy or the LWIP network stack, should not influence our decision to provide command `mii`. Let BOOT_DEFAULTS_CMDS imply MII if either of the network stacks is available. Signed-off-by: Heinrich Schuchardt <[email protected]>
2026-03-12net: airoha: use mt7531 mdio for GDM1Mikhail Kshevetskiy
Current code just bind mt7531 mdio with it's driver, so mdio device may not be probed and hense not usable. This patch: * Forces probing of mt7531 mdio for GDM1 port * Renames the mt7531 mdio bus interface to 'mt7531-mdio'. We may have multiple available MDIO, so the name 'mdio' isn't descriptive enough. * Sets mdio bus for the GDM port device Signed-off-by: Mikhail Kshevetskiy <[email protected]>
2026-03-12net: airoha: makes PCS support optionalMikhail Kshevetskiy
It's not possible to disable PCS support just now, an7581 u-boot will not compile. This patch fixes an issue. Signed-off-by: Mikhail Kshevetskiy <[email protected]>
2026-03-12net: airoha: fill in support for PCS/PHY in Airoha Ethernet driverChristian Marangi
Add required changes to call PCS function to configure the Serdes Port. The Ethernet driver is adapted following Upstream Kernel node structure. Function calling order is the same of Phylink upstream kernel. With the PCS support, also add support for attaching PHY. With "in-band-status" set in DT for the managed property, a rudimental support for SFP module is present. Signed-off-by: Christian Marangi <[email protected]>
2026-03-12configs: enable PCS for Airoha AN7581Christian Marangi
Enable PCS config for Airoha AN7581 SoC by default to enable support for External PHY. Signed-off-by: Christian Marangi <[email protected]>
2026-03-12airoha: add PCS node for AN7581Christian Marangi
Add PCS node for Airoha AN7581 SoC to enable support for Serdes Ethernet and PON port. Signed-off-by: Christian Marangi <[email protected]>
2026-03-12airoha: add GDM1 sub-node into EN7523 ethernet controller nodeMikhail Kshevetskiy
This is required to make ethernet working after PCS support changes Signed-off-by: Mikhail Kshevetskiy <[email protected]>
2026-03-12net: airoha-pcs: an7581: sync with linux code a bitMikhail Kshevetskiy
based on linux kernel patches from https://github.com/Ansuel/openwrt/commits/openwrt-24.10-airoha-an7581-stable/ created by Christian Marangi <[email protected]> Signed-off-by: Mikhail Kshevetskiy <[email protected]>
2026-03-12Merge tag 'mediatek-for-next-2026-03-11' of ↵Tom Rini
https://source.denx.de/u-boot/custodians/u-boot-mediatek into next A fix: * Fixing compiling MT8195 due to some independent changes that were applied around the same time as MT8195 support was merged. (CI would not have caught this since we didn't have a defconfig until now). And few small features: * New defconfig for MT8395/Genio 1200 EVK. * pinctrl support for MT8189-compatible SoCs.
2026-03-12board/raspberrypi: add bcm2712d0-rpi-5-b for Raspberry Pi 5Filip Kokosiński
This commit adds an FDT entry for the d0 stepping of the BCM2712 SoC. This entry is used by the v1.1 revision of the board (revision & 0x0f == 1). Signed-off-by: Filip Kokosiński <[email protected]> Reviewed-by: Peter Robinson <[email protected]> Tested-by: Peter Robinson <[email protected]>
2026-03-12board/raspberrypi: add multi-FDT supportFilip Kokosiński
This patch adds support for multiple FDT files per board model. This is done by adding the FDTFILES macro, which initializes two rpi_model struct members: fdtfiles and fdtcount. The new-style revision codes designate LSB bits as board revision; this value is used to choose between provided FDTs. The first element of the fdtfiles list is used should no revision match. Signed-off-by: Filip Kokosiński <[email protected]> Reviewed-by: Peter Robinson <[email protected]> Tested-by: Peter Robinson <[email protected]>
2026-03-12rpi: pass the Video Core logs DT parameter throughPeter Robinson
Pass the VC logs DT parameter through to the kernel device tree. This is used by the vclog tool and is a useful debugging tool. Signed-off-by: Peter Robinson <[email protected]> Acked-by: Matthias Brugger <[email protected]>
2026-03-12pinctrl: bcm283x: Fix GPIO pull state register values for BCM2711Cibil Pankiras
BCM2711 has different pull-up/down register values compared to BCM2835 - BCM2835: NONE=0, DOWN=1, UP=2 - BCM2711: NONE=0, UP=1, DOWN=2 This patch fixes the pull state register values for BCM2711. Fixes: 2c39d975f87c ("pinctrl: bcm283x: Add GPIO pull-up/down control for BCM2835 and BCM2711") Signed-off-by: Cibil Pankiras <[email protected]> Reviewed-by: Matthias Brugger <[email protected]> Reviewed-by: Peter Robinson <[email protected]> Tested-by: Peter Robinson <[email protected]>
2026-03-12net: airoha: pcs: improve/fix building rulesMikhail Kshevetskiy
pcs-airoha-common.o should not build unconditionally, also make building rules looks better. Signed-off-by: Mikhail Kshevetskiy <[email protected]>
2026-03-12net: airoha: add support for Airoha PCS driverChristian Marangi
Add support for Airoha PCS driver present on AN7581 SoC. This is needed to configure the Serdes port for the different PHY mode. Signed-off-by: Christian Marangi <[email protected]>
2026-03-12net: airoha: init switch before GDM port initializationMikhail Kshevetskiy
Call airoha_switch_init() before creating GDM instances, so if allocation of GDM port fails, early created GDM instances will work normally. Signed-off-by: Mikhail Kshevetskiy <[email protected]>
2026-03-12net: airoha: do not call airoha_fe_init() from GDM port independent codeMikhail Kshevetskiy
We should not call airoha_fe_init() from GDM port independent code, because it do a GDM specific things. Makes airoha_fe_maccr_init() and airoha_fe_init() port dependent and call them from airoha_eth_port_probe() Signed-off-by: Mikhail Kshevetskiy <[email protected]>
2026-03-12net: airoha: declare airoha_eth_port as U_BOOT_DRIVER()Mikhail Kshevetskiy
Declare airoha_eth_port as U_BOOT_DRIVER(), fix airoha_alloc_gdm_port() to lookup a driver instead of direct airoha_eth_port usage. Signed-off-by: Mikhail Kshevetskiy <[email protected]>
2026-03-12net: airoha: avoid out of boundary writing/access to gdm_port_str[] arrayMikhail Kshevetskiy
In the case of an7581 possible GDM port id are: 1, 2 and 4. Initialization of port GDM4 will lead to out of boundary writing to gdm_port_str[] array. Let's increase the array size by 1 to avoid it. Signed-off-by: Mikhail Kshevetskiy <[email protected]>
2026-03-12net: airoha: add initial support for multiple GDM portChristian Marangi
Rework the driver to support multiple GDM port. The driver is split to main driver as a MISC driver with forced probe (by using the DM_FLAG_PROBE_AFTER_BIND) and each GDM port register a ETH driver. This permit a 1:1 implementation with the linux kernel driver and permit to use the same exact DT nodes. Signed-off-by: Christian Marangi <[email protected]>
2026-03-12net: mdio-mt7531-mmio: use common header priv structChristian Marangi
Instead of having duplicate priv struct for mdio-mt7531-mmio driver in both driver and header, use the one exposed by the header directly. This make sure we have consistent priv struct if the driver will be updated in the future. Signed-off-by: Christian Marangi <[email protected]>
2026-03-12common: spl: spl_dfu.c: Fix warning associated with PCI subclass_codeSiddharth Vadapalli
The subclass_code member of the pci_ep_header structure is a 1-byte field. The macro PCI_CLASS_MEMORY_RAM is a concetation of baseclass_code and subclass_code as follows: PCI_BASE_CLASS_MEMORY: 0x05 Subclass Code for RAM: 0x00 PCI_CLASS_MEMORY_RAM: 0x0500 Hence, instead of extracting it via an implicity type conversion from int to u8 which throws a warning, explicitly mask the bits to extract the subclass_code. Fixes: cde77583cf0b ("spl: Add support for Device Firmware Upgrade (DFU) over PCIe") Signed-off-by: Siddharth Vadapalli <[email protected]> Tested-by: Anshul Dalal <[email protected]> Reviewed-by: Mattijs Korpershoek <[email protected]> Tested-by: Mattijs Korpershoek <[email protected]> # am62x_evm_a53 Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Mattijs Korpershoek <[email protected]>
2026-03-12ufs: rockchip: Add device reset supportAlexey Charkov
Wire up the GPIO line which Rockchip RK3576 UFS controller uses to reset the connected UFS device. This seems necessary at least for some UFS modules and fixes the following error while enumerating UFS storage: ufshcd-rockchip ufshc@2a2d0000: ufshcd_link_startup: Device not present ufshcd-rockchip ufshc@2a2d0000: link startup failed -6 ufshcd-rockchip ufshc@2a2d0000: ufshcd_pltfrm_init() failed -6 Note that the GPIO descriptor for device resets is already required by the DT binding (link enclosed). Link: https://elixir.bootlin.com/linux/v6.18.5/source/Documentation/devicetree/bindings/ufs/rockchip,rk3576-ufshc.yaml#L70 Fixes: 76465ce21ee4 ("ufs: rockchip: Add initial support") Reviewed-by: Neil Armstrong <[email protected]> Reviewed-by: Shawn Lin <[email protected]> Signed-off-by: Alexey Charkov <[email protected]> Link: https://patch.msgid.link/[email protected] Signed-off-by: Neil Armstrong <[email protected]>
2026-03-12spl: Make UFS available for SPL buildsAlexey Charkov
Add minimal infrastructure to build SPL images with support for UFS storage devices. This also pulls in SCSI support and charset functions, which are dependencies of the UFS code. With this, only a fixed offset is supported for loading the next image, which should be specified in CONFIG_SPL_UFS_RAW_U_BOOT_SECTOR as the number of 4096-byte sectors into the UFS block device. Reviewed-by: Neil Armstrong <[email protected]> Signed-off-by: Alexey Charkov <[email protected]> Link: https://patch.msgid.link/[email protected] Signed-off-by: Neil Armstrong <[email protected]>
2026-03-11pinctrl: mediatek: add support for mt8189Bo-Chen Chen
Add pinctrl support for mt8189. Signed-off-by: Bo-Chen Chen <[email protected]> Co-developed-by: David Lechner <[email protected]> Reviewed-by: Macpaul Lin <[email protected]> Link: https://patch.msgid.link/[email protected] Signed-off-by: David Lechner <[email protected]>
2026-03-11pinctl: mediatek: increase max number of base addressesDavid Lechner
Increase the maximum number of base addresses that can be handled by the mediatek pinctrl driver from 10 to 15. This is needed for the MT8189 which has 15 base addresses. Reviewed-by: Macpaul Lin <[email protected]> Link: https://patch.msgid.link/[email protected] Signed-off-by: David Lechner <[email protected]>
2026-03-11pinctl: mediatek: add bounds check on number of base addressesDavid Lechner
Add a bounds check on the number of base addresses to prevent out-of-bounds access to the priv->base array. Reviewed-by: Macpaul Lin <[email protected]> Link: https://patch.msgid.link/[email protected] Signed-off-by: David Lechner <[email protected]>
2026-03-10kbuild: fix cross_tools compilationIlias Apalodimas
Frieder reports that after the kbuild sync running make tools-only_defconfig make cross_tools fails with UPD include/generated/timestamp_autogenerated.h PYMOD rebuild tools/Makefile:359: *** insufficient number of arguments (1) to function 'filter'. Stop. make: *** [Makefile:2191: tools] Error 2 After the sync 'hostprogs-always-y' contains the complete list of the tools we need to strip, so the $(filter) command is not needed. Fixes: bd3f9ee679b4d ("kbuild: Bump the build system to 6.1") Reported-by: Frieder Schrempf <[email protected]> Signed-off-by: Ilias Apalodimas <[email protected]> Tested-by: Frieder Schrempf <[email protected]>
2026-03-10arm: k3: Kconfig: Enable fTPM and RPMB supportShiva Tripathi
Enable firmware TPM (fTPM) support via OP-TEE for K3 platforms with MMC hardware. This provides TPM 2.0 functionality through Microsoft's fTPM Trusted Application running in OP-TEE secure world, using eMMC RPMB as persistent storage. fTPM support in U-Boot provides the foundation for measured boot and disk encryption use cases. The ARM64 condition ensures these apply only to A53/A72 cores and the MMC condition ensures fTPM is enabled only on platforms with eMMC hardware support. Signed-off-by: Shiva Tripathi <[email protected]> Acked-by: Andrew Davis <[email protected]>
2026-03-10scripts: add checkkconfigsymbols.pyHeinrich Schuchardt
Add checkkconfigsymbols.py from Linux 7.0-rc1 (unchanged since v6.2). This tool allows to identify the usage of symbols that are not defined in Kconfig. Suggested-by: Ilias Apalodimas <[email protected]> Signed-off-by: Heinrich Schuchardt <[email protected]> Acked-by: Ilias Apalodimas <[email protected]> Reviewed-by: Quentin Schulz <[email protected]>
2026-03-10disk: fix DOS_PARTITION dependenciesHeinrich Schuchardt
* The symbol for the x86 architecture is CONFIG_X86 and not CONFIG_x86. * Correct the description. The partition type is called MBR. Signed-off-by: Heinrich Schuchardt <[email protected]> Reviewed-by: Tom Rini <[email protected]>
2026-03-10sandbox: don't imply non-existent CONFIG_KEYBOARDHeinrich Schuchardt
Symbol CONFIG_KEYBOARD does not exist. Don't imply it. Signed-off-by: Heinrich Schuchardt <[email protected]> Reviewed-by: Quentin Schulz <[email protected]>
2026-03-10boot: don't select non-existent CONFIG_VPL_CRYPTOHeinrich Schuchardt
Symbol CONFIG_VPL_CRYPTO does not exist. Don't select it. Signed-off-by: Heinrich Schuchardt <[email protected]> Fixes: 4218456b3fac ("vbe: Add Kconfig options for VPL") Reviewed-by: Quentin Schulz <[email protected]>
2026-03-10dma: ti: don't use non-existent CONFIG_TI_K3_NAVSS_PSILCFGHeinrich Schuchardt
Symbol CONFIG_TI_K3_NAVSS_PSILCFG does not exist. Don't select it. Signed-off-by: Heinrich Schuchardt <[email protected]>
2026-03-10arm/mach-sc5xx: don't select non-existent GIC_600_CLEAR_RDPDHeinrich Schuchardt
The symbol CONFIG_GIC_600_CLEAR_RDPD does not exist. Don't select it. Signed-off-by: Heinrich Schuchardt <[email protected]> Fixes: 48a0b0b4b7d7 ("arch: arm: Add Analog Devices SC5xx machine type") Fixes: 03de305ec48b ("Restore patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"") Reviewed-by: Quentin Schulz <[email protected]> Reviewed-by: Greg Malysa <[email protected]>
2026-03-10arm: don't select non-existent CONFIG_DM_PCIHeinrich Schuchardt
We removed configuration symbol CONFIG_DM_PCI with commit 3232bdf0b30b ("pci: Drop DM_PCI"). Don't select it for TARGET_POMELO. Fixes: b9d0f00a9d3f ("arm: add initial support for the Phytium Pomelo Board") Signed-off-by: Heinrich Schuchardt <[email protected]> Reviewed-by: Tom Rini <[email protected]>
2026-03-10Merge patch series "fs: fat: Handle 'FAT sector size mismatch'"Tom Rini
Varadarajan Narayanan <[email protected]> says: The disk_read() and disk_write() functions of the FAT driver use the blk_dread() and blk_dwrite() respectively. The blk_* APIs read and write to the devices in terms of the device block size. However, the FAT driver reads in terms of the device block size (from fat_set_blk_dev and read_bootsectandvi) and sector size in the rest of the places. This causes buffer overflows or partial reads when the FAT sector size is not equal to device block size. Fix this by using blk_dread in fat_set_blk_dev and read_bootsectandvi instead of disk_read. And update disk_read/disk_write to handle FAT sector size and block size mismatch. Tested on blksz | FAT sector size ------+---------------- 4096 | 4096 512 | 512 4096 | 512 512 | 4096 CI test results --------------- https://github.com/u-boot/u-boot/pull/871 All checks have passed 93 successful checks No conflicts with base branch Code size change info --------------------- arm: (for 1/1 boards) all +32.0 text +32.0 qemu_arm : all +32 text +32 u-boot: add: 0/0, grow: 2/0 bytes: 24/0 (24) function old new delta read_bootsectandvi 420 432 +12 fat_set_blk_dev 204 216 +12 aarch64: (for 1/1 boards) all +12.0 rodata -8.0 text +20.0 qemu_arm64 : all +12 rodata -8 text +20 u-boot: add: 0/0, grow: 2/0 bytes: 20/0 (20) function old new delta read_bootsectandvi 408 420 +12 fat_set_blk_dev 204 212 +8 aarch64: (for 1/1 boards) all -2.0 data -8.0 rodata +6.0 qcom_qcs9100 : all -2 data -8 rodata +6 u-boot: add: 1/-1, grow: 8/-1 bytes: 708/-224 (484) function old new delta disk_rw - 628 +628 read_bootsectandvi 408 428 +20 fat_itr_root 500 520 +20 get_cluster 376 388 +12 set_contents 2076 2084 +8 fat_set_blk_dev 204 212 +8 static.set_fatent_value 536 540 +4 get_fatent 420 424 +4 fat_next_cluster 368 372 +4 disk_read 100 - -100 disk_write 132 8 -124 Link: https://lore.kernel.org/r/[email protected]
2026-03-10configs: qcom: Enable FS_FAT_HANDLE_SECTOR_SIZE_MISMATCHVaradarajan Narayanan
Enable FS_FAT_HANDLE_SECTOR_SIZE_MISMATCH to handle the different combination of FAT sector size and device block size present in QCOM platforms. Signed-off-by: Varadarajan Narayanan <[email protected]>
2026-03-10fs: fat: Handle 'FAT sector size mismatch'Varadarajan Narayanan
The disk_read() and disk_write() functions of the FAT driver use the blk_dread() and blk_dwrite() respectively. The blk_* APIs read and write to the devices in terms of the device block size. However, the FAT driver reads in terms of the device block size (from fat_set_blk_dev and read_bootsectandvi) and sector size in the rest of the places. This causes buffer overflows or partial reads when the FAT sector size is not equal to device block size. Fix this by using blk_dread in fat_set_blk_dev and read_bootsectandvi instead of disk_read. And update disk_read/disk_write to handle FAT sector size and block size mismatch. Tested on blksz | FAT sector size ------+---------------- 4096 | 4096 512 | 512 4096 | 512 512 | 4096 Signed-off-by: Varadarajan Narayanan <[email protected]>
2026-03-10Merge tag 'u-boot-rockchip-20260309' of ↵Tom Rini
https://source.denx.de/u-boot/custodians/u-boot-rockchip into next CI: https://source.denx.de/u-boot/custodians/u-boot-rockchip/-/pipelines/29452 - New SoC support: RK3506, RK3582; - New Board support: RK3528 FriendlyElec NanoPi Zero2; - Other fixes
2026-03-10arm: rockchip: don't use non-existent CONFIG_TPL_TINY_FRAMEWORKHeinrich Schuchardt
Symbol CONFIG_TPL_TINY_FRAMEWORK does not exist. Don't select it. Signed-off-by: Heinrich Schuchardt <[email protected]> Reviewed-by: Quentin Schulz <[email protected]> Reviewed-by: Kever Yang <[email protected]>
2026-03-10rockchip: Reduce size of ramboot usb472 payloadJonas Karlman
Booting into SPL using ramboot can take several seconds on some SoCs due to the large size of the usb472 payload sent over USB to BootROM. A large chunk of the usb472 payload, around 1-2 MiB, is padding used to avoid overlapping when loading e.g. TF-A to 0x40000. BootROM is likely wasting unnecessary time crc16 validating the padding of the payload. Place the FIT payload directly after SPL and memmove it to the expected memory location, SPL_LOAD_FIT_ADDRESS, to avoid excessive padding and help speed up ramboot. Binman symbols are used to get the position and size of the FIT payload that is initially loaded into DRAM by the BootROM. Signed-off-by: Jonas Karlman <[email protected]> Reviewed-by: Kever Yang <[email protected]>