u-boot.git/arch/arm/mach-rockchip, branch master

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: spl: Add support for booting from UFS

2026-06-08T13:32:40Z

Add the required architecture-specific lookups to enable U-boot SPL to load images from UFS storage devices on Rockchip RK3576, which has a boot ROM capable of loading the SPL image from UFS. Reviewed-by: Jonas Karlman Signed-off-by: Alexey Charkov

board: rockchip: Add FriendlyElec NanoPi R76S

2026-06-08T13:22:19Z

The NanoPi R76S (as "R76S") is an open-sourced mini IoT gateway device with two 2.5G, designed and developed by FriendlyElec. Features tested on a NanoPi R76S 2411: - SD-card boot - eMMC boot - LEDs and button - PCIe/Ethernet - USB host Signed-off-by: Jonas Karlman Reviewed-by: Kever Yang

arm: Remove redundant "xPL_SYS_MALLOC_F default y" entries

2026-04-07T21:26:43Z

The symbol SPL_SYS_MALLOC_F defaults to y when visible and TPL_SYS_MALLOC_F defaults to y when visible and SPL_SYS_MALLOC_F is enabled. Remove the places from Kconfig files that had unneccsary "default y" for these options. Signed-off-by: Tom Rini

global: Audit Kconfig usage of PARTITION_TYPE_GUID

2026-04-03T18:06:10Z

It is not functionally possible to use the code enabled by PARTITION_TYPE_GUID without having EFI_PARTITION be enabled as well. Not all users of the former had ensured that the latter was enabled however, so audit all current users and then as appropriate select or imply EFI_PARTITION as needed. Signed-off-by: Tom Rini

rockchip: rk3568: Include all addressable DRAM in memory map

2026-03-13T22:17:15Z

Rockchip RK356x supports up to 8 GiB DRAM, however U-Boot only includes the initial 32-bit 0-4 GiB addressable range in its memory map, something that matches gd->ram_top and current expected memory available for use in U-Boot. The vendor DRAM init blobs add following ddr_mem rk atags [1]: 4 GiB: [0x0, 0xf0000000) and [0x1f0000000, 0x200000000) 8 GiB: [0x0, 0x200000000) Add the remaining 64-bit 4-8 GiB addressable range, that already is reported to OS, to the U-Boot memory map to more correctly describe all available and addressable DRAM of RK356x. While at it also add the missing UL suffix to the PCIe address range for consistency. [1] https://gist.github.com/Kwiboo/6d983693c79365b43c330eb3191cbace Acked-by: Quentin Schulz Signed-off-by: Jonas Karlman Reviewed-by: Kever Yang

arm: rockchip: don't use non-existent CONFIG_TPL_TINY_FRAMEWORK

2026-03-10T16:07:03Z

Symbol CONFIG_TPL_TINY_FRAMEWORK does not exist. Don't select it. Signed-off-by: Heinrich Schuchardt Reviewed-by: Quentin Schulz Reviewed-by: Kever Yang

rockchip: Reduce size of ramboot usb472 payload

2026-03-10T16:07:03Z

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 Reviewed-by: Kever Yang

rockchip: rk3588: include all addressable DRAM in memory map

2026-03-10T16:07:03Z

The ATAGS set by Rockchip DDR init blob[1] specify DRAM banks above the first addressable 4GiB which we haven't done in the mem_map for RK3588 yet. For 4GiB DRAM, the 256MiB missing from the first addressable 4GiB (due to MMIO) are accessible at the end of the 8GiB address space. For 8GiB, 4-8GiB address space is used for the additional 4GiB and the missing 256MiB are at the end of 12GiB address space. For 12, 4-12GiB and the missing 256MiB at the end of 20GiB address space. For 16GiB, 4-~16GiB with two holes (reasons unknown) around 16GiB and the missing 256MiB is at the end of 20GiB address space. For 32GiB, 4-16~GiB with two holes and then 16GiB to 32GiB address space (so likely missing 256MiB from MMIO address space). [1] https://gist.github.com/Kwiboo/1c020d37e3adbc9d0d79dc003d921977 Suggested-by: Jonas Karlman Signed-off-by: Quentin Schulz Reviewed-by: Kever Yang