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

mach-snapdragon: of_fixup: Add OP-TEE DT fixup support

2026-04-27T10:38:44Z

Add support for OP-TEE live tree DT fixup support which enables U-Boot OP-TEE driver to be probed. As well as the EFI DT fixup protocol allows the live tree fixup to be carried over to the OS for the OP-TEE driver in the OS to probe as well. Note that this fixup only gets applied if OP-TEE support is detected via checking for OP-TEE message UID. Signed-off-by: Sumit Garg Link: https://patch.msgid.link/20260127062341.723966-3-sumit.garg@kernel.org Signed-off-by: Casey Connolly

arch: arm: mach-snapdragon: Auto-detect USB SSPHY driver support

2026-04-27T10:38:44Z

Automatically detect super-speed USB PHY driver availability and skip the USB speed fixup if driver is available, eliminating the need for manual configuration. Previously, U-Boot unconditionally limited USB to high-speed mode on all Qualcomm platforms because most lacked super-speed PHY drivers. This change implements runtime detection that checks if a PHY driver exists for the super-speed PHY node referenced by the DWC3 controller. The fixup is automatically skipped when a compatible driver is found, allowing the hardware to operate at full capability. Platforms without super-speed PHY drivers continue to receive the fixup automatically. Signed-off-by: Balaji Selvanathan [casey: rebased on flat-dwc3 dt support + fix Balaji's signoff] [casey: make erroneous printf() a debug() again] Link: https://patch.msgid.link/20251203110735.1959862-5-balaji.selvanathan@oss.qualcomm.com Signed-off-by: Casey Connolly

mach-snapdragon: allocate memory for DT overlays

2026-04-27T10:33:30Z

Allocate a 1 MiB LMB region for fdtoverlay_addr_r when CONFIG_OF_LIBFDT_OVERLAY is enabled, allowing runtime application of DT overlays on Snapdragon platforms. This is useful for Android-based boot flows where the final DT passed to the kernel must contain modified /firmware/android/fstab entries. One use case is redirecting system and vendor partitions to microSD storage instead of internal eMMC without rebuilding the base DTB. The allocation is conditional on CONFIG_OF_LIBFDT_OVERLAY and has no effect on boards that do not enable overlay support. Signed-off-by: Antony Kurniawan Soemardi Reviewed-by: Sumit Garg Reviewed-by: Casey Connolly Link: https://patch.msgid.link/20260217-qcom-fdt-overlay-v1-1-d0fa0e70d738@smankusors.com Signed-off-by: Casey Connolly

mach-snapdragon: Remove RPMH power domain DT fixup code

2026-04-27T10:33:29Z

Remove the device tree fixup code that was stripping power-domains properties from device tree nodes. This fixup was a temporary workaround needed when RPMH power domain driver support was not available in U-Boot. Now that RPMH power domain driver support has been added, the power domain properties can be preserved in the device tree, allowing proper power domain management. If a suitable power domain driver is not found for the power-controller node, it will be handled with a warning in dev_power_domain_ctrl(). Reviewed-by: Varadarajan Narayanan Signed-off-by: Aswin Murugan Reviewed-by: Sumit Garg Link: https://patch.msgid.link/20260213111009.1254360-4-aswin.murugan@oss.qualcomm.com Signed-off-by: Casey Connolly

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

mach-snapdragon: of_fixup: support new flat dwc3 node

2026-01-14T15:25:09Z

Qualcomm DTs are being updated to use a new format where the dwc3 glue node and controller are combined into a single DT node. Update the fixup code to handle this case. Reviewed-by: Neil Armstrong Link: https://patch.msgid.link/20260114135739.1546815-1-casey.connolly@linaro.org Signed-off-by: Casey Connolly

mach-snapdragon: capsule_update: Fix eMMC detection for non-UFS devices

2026-01-14T15:25:09Z

Currently (since 2026.01-rc) on all SDM630/660 based devices this is printed, after observing long boot delay (several seconds) before executing preboot commands: QCOM-FMP: Failed to find boot partition find_target_partition() function incorrectly assumes that eMMC is always at number 0. In general you can't rely on device numbering to determine if particular block device is eMMC or SD-card, because it depends on how aliases are defined in device tree "chosen" node. Some SoCs have MMC numbers starting at 1, not 0; so mmc1 is eMMC, mmc2 is SD-card. Make eMMC detection reliable by using IS_SD() macro from mmc.h header. Using this method target boot partition can be found successfully. With debug prints enabled, this is printed: QCOM-FMP: skipped SD-Card (devnum 2) QCOM-FMP: Capsule update target: boot (disk 1:60) QCOM-FMP: DFU string: 'mmc 0=u-boot.bin part 1 60' Without debug prints nothing is printed, no error about failure to find boot partition. Fixes: fe80a5f80095 ("mach-snapdragon: CapsuleUpdate: support all boot methods") Signed-off-by: Alexey Minnekhanov Reviewed-by: Casey Connolly Link: https://patch.msgid.link/20251107232935.283843-1-alexeymin@minlexx.ru Signed-off-by: Casey Connolly

mach-snapdragon: fix erroneous lmb allocations

2025-08-13T13:14:04Z

In commit 6e4675b8e5d8 ("lmb: replace the lmb_alloc() and lmb_alloc_base() API's") an additional allocation was mistakenly introduced resulting in ${kernel_comp_size} containing the address of a second 64mb region rather than the actual value of KERNEL_COMP_SIZE. Additionally, in commit b40d7b8f72f1 ("Merge patch series "lmb: use a single API for all allocations"") merge conflict resulted in an additional 128mb allocation for ${loadaddr} when CONFIG_FASTBOOT is enabled, where it should actually be set to the same value as ${fastboot_addr_r} to respect size constraints (and since it doesn't seem to interfer with any bootflows). Fixup both of these, freeing up 192mb of memory. Fixes: 6e4675b8e5d8 ("lmb: replace the lmb_alloc() and lmb_alloc_base() API's") Fixes: b40d7b8f72f1 ("Merge patch series "lmb: use a single API for all allocations"") Link: https://lore.kernel.org/r/20250811104710.1896382-1-casey.connolly@linaro.org Signed-off-by: Casey Connolly

treewide: fix Casey's name

2025-07-28T14:53:20Z

I updated the mailmap a while back but it's nice to have authorship comments adjusted too. Signed-off-by: Casey Connolly

Merge patch series "lmb: use a single API for all allocations"

2025-06-25T15:57:01Z

Sughosh Ganu says: The LMB module has a bunch for API's which are used for allocating memory. There are a couple of API's for requesting memory, and two more for reserving regions of memory. Replace these different API's with a single one, lmb_alloc_mem(). The type of allocation to be made is specified through one of the parameters to the function. Additionally, the two API's for reserving regions of memory, lmb_reserve() and lmb_alloc_addr() are the same with one difference. One can reserve any memory region with lmb_reserve(), while lmb_alloc_addr() actually checks that the memory region being requested is part of the LMB memory map. Reserving memory that is not part of the LMB memory map is pretty futile -- the allocation functions do not allocate memory which has not been added to the LMB memory map. This series also removes the functionality allowing for reserving memory regions outside the LMB memory map. Any request for reserving a region of memory outside the LMB memory map now returns an -EINVAL error. Certain places in the common code using the LMB API's were not checking the return value of the functions. Checks have been added for them. There are some calls being made from the architecture/platform specific code which too do not check the return value. Those have been kept the same, as I do not have the platform with me to check if it causes any issues on those platforms. In addition, there is a patch which refactors code in lmb_overlaps_region() and lmb_can_reserve_region() so that both functionalities can be put in a single function, lmb_overlap_checks(). Finally, a new patch has been added which checks the return value of the lmb allocation function before copying the device-tree to the allocated address. Link: https://lore.kernel.org/r/20250617104346.1379981-1-sughosh.ganu@linaro.org [trini: Rework arch/arm/mach-snapdragon/board.c merge] Signed-off-by: Tom Rini