arm: snapdragon: Add snagboot support for Lemans-EVK
v2 cover arm: snapdragon: Add snagboot support for Lemans-EVK
This series adds support for running U-Boot in snagboot mode on Qualcomm Snapdragon platforms, targeting the Lemans-EVK board.
In snagboot mode, XBL loads U-Boot directly without initializing PSCI firmware or populating the Command DB. U-Boot then enters fastboot immediately, enabling partition flashing for manufacturing and recovery use cases.
Patch 1 changes SYSRESET_PSCI from 'select' to 'imply' so it can be disabled on platforms where PSCI firmware is unavailable.
Patch 2 guards show_psci_version() and qcom_psci_fixup() with CONFIG_ARM_SMCCC to prevent build failures when SMCCC is disabled.
Patch 3 disables the MMU and invalidates TLBs at the earliest entry point to clear stale page tables left by previous bootloader before U-Boot sets up its own MMU.
Patch 4 adds QCOM_COMMAND_DB_OPTIONAL to allow the CMD DB driver to bind successfully when CMD DB data is not populated by XBL, logging a warning instead of failing.
Patch 5 adds qcom_lemans_snagboot_defconfig for Lemans-EVK, based on qcom_defconfig with snagboot-specific settings: SCSI-backed environment, optional CMD DB, PSCI reset disabled, and a bootcmd that auto-enters fastboot over USB with zero boot delay.
Patch 6 adds the new defconfig to the ARM SNAPDRAGON section in MAINTAINERS.
---
Changes in v2:
- Changed SYSRESET_PSCI from 'select' to 'imply'
- Guard show_psci_version() and qcom_psci_fixup() with CONFIG_ARM_SMCCC
- Disables the MMU and invalidates TLBs at the earliest entry point
- Add qcom_lemans_snagboot_defconfig for Lemans-EVK
- Link to v1: https://lore.kernel.org/u-boot/[email protected]/
---
Balaji Selvanathan (6):
arm: snapdragon: Make SYSRESET_PSCI optional
arm: snapdragon: Guard PSCI functions with CONFIG_ARM_SMCCC
arm: snapdragon: Disable MMU early before U-Boot reset vector
soc: qcom: cmd-db: Allow boot without CMD DB data
configs: add qcom_lemans_snagboot_defconfig for Lemans-EVK
MAINTAINERS: add qcom_lemans_snagboot_defconfig to ARM SNAPDRAGON
MAINTAINERS | 1 + arch/arm/Kconfig | 2 +- arch/arm/mach-snapdragon/board.c | 14 ++++++++ arch/arm/mach-snapdragon/include/mach/boot0.h | 46 +++++++++++++++++++++++++ configs/qcom_lemans_snagboot_defconfig | 49 +++++++++++++++++++++++++++ drivers/soc/qcom/Kconfig | 16 +++++++++ drivers/soc/qcom/cmd-db.c | 10 ++++++ 7 files changed, 137 insertions(+), 1 deletion(-)
---
base-commit: 26fe27b4eaddcf73e4472368a71703a68e2f67d9
change-id: 20260608-snagboot-df4b6a79a086
Best regards,
Signature · 1 line
Balaji Selvanathan <[email protected]>
PATCH v2 1/6 arm: snapdragon: Make SYSRESET_PSCI optional
In snagboot mode, U-Boot is loaded directly by XBL without a prior bootloader to initialize PSCI firmware. Forcing SYSRESET_PSCI via 'select' causes failures in this scenario. Change to 'imply' to allow it to be disabled when PSCI is unavailable.
---
Changes in v2:
- Newly introduced in v2
--- arch/arm/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/Kconfig +1 -1
@@ -1150,7 +1150,7 @@ config ARCH_SNAPDRAGON select SAVE_PREV_BL_FDT_ADDR if !ENABLE_ARM_SOC_BOOT0_HOOK select LINUX_KERNEL_IMAGE_HEADER if !ENABLE_ARM_SOC_BOOT0_HOOK select SYSRESET - select SYSRESET_PSCI + imply SYSRESET_PSCI select ANDROID_BOOT_IMAGE_IGNORE_BLOB_ADDR select MMU_PGPROT imply OF_UPSTREAM
Signature · 1 line
2.34.1
Re: [PATCH v2 1/6] arm: snapdragon: Make SYSRESET_PSCI optional
Quoted 6 lines · Balaji Selvanathan
In snagboot mode, U-Boot is loaded directly by XBL without a prior bootloader to initialize PSCI firmware. Forcing
SYSRESET_PSCIvia 'select' causes failures in this scenario. Change to 'imply' to allow it to be disabled when PSCI is unavailable.Signed-off-by Balaji Selvanathan <[email protected]>
Quoted 24 lines
---
Changes in v2:
- Newly introduced in v2--- arch/arm/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)arch/arm/Kconfig +1
-2@@ -1150,7 +1150,7 @@ config ARCH_SNAPDRAGON select SAVE_PREV_BL_FDT_ADDR if !ENABLE_ARM_SOC_BOOT0_HOOK select LINUX_KERNEL_IMAGE_HEADER if !ENABLE_ARM_SOC_BOOT0_HOOK select SYSRESET - select SYSRESET_PSCI + imply SYSRESET_PSCI select ANDROID_BOOT_IMAGE_IGNORE_BLOB_ADDR select MMU_PGPROT imply OF_UPSTREAM --2.34.1
PATCH v2 2/6 arm: snapdragon: Guard PSCI functions with CONFIG_ARM_SMCCC
In reply to Balaji SelvanathanIn snagboot mode, U-Boot is loaded directly by XBL without PSCI firmware support. The functions show_psci_version() and qcom_psci_fixup() call arm_smccc_smc() which is unavailable when CONFIG_ARM_SMCCC is disabled, causing build failures.
Wrap both functions with CONFIG_ARM_SMCCC guards and provide empty inline stubs for the disabled case.
---
Changes in v2:
- Newly introduced in v2
--- arch/arm/mach-snapdragon/board.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
arch/arm/mach-snapdragon/board.c +14 -0
@@ -158,6 +158,7 @@ static int qcom_parse_memory(const void *fdt)return 0 ; } +#ifdef CONFIG_ARM_SMCCC static void show_psci_version (void ) {struct arm_smccc_res res;
@@ -172,6 +173,12 @@ static void show_psci_version(void)PSCI_VERSION_MAJOR (res.a0), PSCI_VERSION_MINOR(res.a0)); } +#else +static inline void show_psci_version (void ) +{ +/* PSCI not available - no-op */ +} +#endif /** * Most MSM8916 devices in the wild shipped without PSCI support, but the
@@ -180,6 +187,7 @@ static void show_psci_version(void)* firmware driver doesn't bind (which then binds a sysreset driver that won't * work). */ +#ifdef CONFIG_ARM_SMCCC static void qcom_psci_fixup (void *fdt) {int offset, ret;
@@ -199,6 +207,12 @@ static void qcom_psci_fixup(void *fdt)if (ret) log_err("Failed to delete /psci node: %d\n", ret); } +#else +static inline void qcom_psci_fixup (void *fdt) +{ +/* PSCI not available - no-op */ +} +#endif /* We support booting U-Boot with an internal DT when running as a first-stage bootloader * or for supporting quirky devices where it's easier to leave the downstream DT in place
Signature · 1 line
2.34.1
Re: [PATCH v2 2/6] arm: snapdragon: Guard PSCI functions with CONFIG_ARM_SMCCC
Quoted 29 lines · Balaji Selvanathan
In snagboot mode, U-Boot is loaded directly by XBL without PSCI firmware support. The functions
show_psci_version()andqcom_psci_fixup()callarm_smccc_smc()which is unavailable whenCONFIG_ARM_SMCCCis disabled, causing build failures.Wrap both functions with
CONFIG_ARM_SMCCCguards and provide empty inline stubs for the disabled case.Signed-off-by Balaji Selvanathan <[email protected]>---
Changes in v2:
- Newly introduced in v2--- arch/arm/mach-snapdragon/board.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)arch/arm/mach-snapdragon/board.c +1
-0@@ -158,6 +158,7 @@ static int qcom_parse_memory(const void *fdt)return 0 ; } +#ifdef CONFIG_ARM_SMCCC static void show_psci_version (void ) {struct arm_smccc_res res;
arch/arm/mach-snapdragon/board.c static void show_psci_version(void) · line 181
Quoted 9 lines
arch/arm/mach-snapdragon/board.c +6
-0@@ -172,6 +173,12 @@ static void show_psci_version(void)PSCI_VERSION_MAJOR (res.a0), PSCI_VERSION_MINOR(res.a0)); } +#else +static inline void show_psci_version (void ) +{ +/* PSCI not available - no-op */ +} +#endif
static void show_psci_version(void)
{
if (!IS_ENABLED(CONFIG_ARM_SMCCC))
return;
. . .
}Wouldn't this work? Didn't checkpatch complain?
Quoted 12 lines
arch/arm/mach-snapdragon/board.c +1
-0/** * Most MSM8916 devices in the wild shipped without PSCI support, but the @@ -180,6 +187,7 @@ static void show_psci_version(void)* firmware driver doesn't bind (which then binds a sysreset driver that won't * work). */ +#ifdef CONFIG_ARM_SMCCC static void qcom_psci_fixup (void *fdt) {int offset, ret;
arch/arm/mach-snapdragon/board.c static void qcom_psci_fixup(void *fdt) · line 215
Quoted 9 lines
arch/arm/mach-snapdragon/board.c +6
-0@@ -199,6 +207,12 @@ static void qcom_psci_fixup(void *fdt)if (ret) log_err("Failed to delete /psci node: %d\n", ret); } +#else +static inline void qcom_psci_fixup (void *fdt) +{ +/* PSCI not available - no-op */ +} +#endif
Same here.
-Varada
Quoted 7 lines
arch/arm/mach-snapdragon/board.c +0
-1/* We support booting U-Boot with an internal DT when running as a first-stage bootloader * or for supporting quirky devices where it's easier to leave the downstream DT in place -- 2.34.1
PATCH v2 3/6 arm: snapdragon: Disable MMU early before U-Boot reset vector
In reply to Balaji SelvanathanWhen U-Boot is loaded by XBL in snagboot mode, XBL leaves the MMU enabled with its own page tables. This causes stale TLB entries and incorrect memory mappings when U-Boot initializes its own MMU.
Disable the MMU and invalidate TLBs at the earliest entry point, before branching to the reset vector, handling EL1, EL2, and EL3. This ensures a clean MMU state for U-Boot initialization.
The changes in this patch are based on:
https://lore.kernel.org/all/[email protected]/
https://lore.kernel.org/u-boot/[email protected]/
---
Changes in v2:
- Newly introduced in v2
--- arch/arm/mach-snapdragon/include/mach/boot0.h | 46 +++++++++++++++++++++++++++ 1 file changed, 46 insertions(+)
arch/arm/mach-snapdragon/include/mach/boot0.h +46 -0
@@ -8,6 +8,52 @@ #elif defined(CONFIG_QCOM_EL2_GUNYAH_EXIT_SUPPORT) #include "gunyah_exit_boot0.h" #else + /* + * Disable MMU at the earliest possible point. + * This must be done before any other U-Boot code executes. + * Handle all exception levels (EL1, EL2, EL3). + * + * After disabling MMU, invalidate TLB to clear any stale entries + * that might cause issues when MMU is re-enabled later. + */ + mrs x0, CurrentEL + cmp x0, #(3 << 2) /* EL3? */ + b.eq disable_mmu_el3 + cmp x0, #(2 << 2) /* EL2? */ + b.eq disable_mmu_el2 + /* EL1 */ + mrs x0, sctlr_el1 + bic x0, x0, #1 /* Clear M bit (MMU enable) */ + msr sctlr_el1, x0 + isb + /* Invalidate TLB for EL1 */ + tlbi vmalle1 + dsb sy + isb + b mmu_disabled +disable_mmu_el3: + mrs x0, sctlr_el3 + bic x0, x0, #1 /* Clear M bit (MMU enable) */ + bic x0, x0, #(1 << 19) /* Clear WXN bit (Write XOR Execute) */ + msr sctlr_el3, x0 + isb + /* Invalidate entire TLB for all ELs */ + tlbi alle3 + dsb sy + isb + b mmu_disabled +disable_mmu_el2: + mrs x0, sctlr_el2 + bic x0, x0, #1 /* Clear M bit (MMU enable) */ + msr sctlr_el2, x0 + isb + /* Invalidate TLB for EL2 */ + tlbi alle2 + dsb sy + isb +mmu_disabled: + b reset + #endif #endif
Signature · 1 line
2.34.1
Re: [PATCH v2 3/6] arm: snapdragon: Disable MMU early before U-Boot reset vector
Quoted 25 lines · Balaji Selvanathan
When U-Boot is loaded by XBL in snagboot mode, XBL leaves the MMU enabled with its own page tables. This causes stale TLB entries and incorrect memory mappings when U-Boot initializes its own MMU.
Disable the MMU and invalidate TLBs at the earliest entry point, before branching to the reset vector, handling EL1, EL2, and EL3. This ensures a clean MMU state for U-Boot initialization.
The changes in this patch are based on:
https://lore.kernel.org/all/[email protected]/
https://lore.kernel.org/u-boot/[email protected]/Signed-off-by Balaji Selvanathan <[email protected]>---
Changes in v2:
- Newly introduced in v2--- arch/arm/mach-snapdragon/include/mach/boot0.h | 46 +++++++++++++++++++++++++++ 1 file changed, 46 insertions(+)arch/arm/mach-snapdragon/include/mach/boot0.h +0
-0
arch/arm/mach-snapdragon/include/mach/boot0.h line 10
Quoted 3 lines
arch/arm/mach-snapdragon/include/mach/boot0.h +0
-0@@ -8,6 +8,52 @@#elif defined(CONFIG_QCOM_EL2_GUNYAH_EXIT_SUPPORT )#include "gunyah_exit_boot0.h" #else
Since this is needed only for snagboot, should this be inside some ifdef?
Quoted 4 lines
arch/arm/mach-snapdragon/include/mach/boot0.h +4
-0+/* +* Disable MMU at the earliest possible point. +* This must be done before any other U-Boot code executes. +* Handle all exception levels (EL1, EL2, EL3).
arch/arm/mach-snapdragon/include/mach/boot0.h line 24
Quoted 10 lines
arch/arm/mach-snapdragon/include/mach/boot0.h +10
-0+* +* After disabling MMU, invalidate TLB to clear any stale entries +* that might cause issues when MMU is re-enabled later. +*/ +mrs x0, CurrentEL + cmp x0, #(3 << 2) /* EL3? */ + b.eq disable_mmu_el3 + cmp x0, #(2 << 2) /* EL2? */ + b.eq disable_mmu_el2 +/* EL1 */
Not sure if it is better to confirm EL1 and raise error if it is in EL0.
-Varada
arch/arm/mach-snapdragon/include/mach/boot0.h line 33
Quoted 9 lines
arch/arm/mach-snapdragon/include/mach/boot0.h +9
-0+mrs x0, sctlr_el1 + bic x0, x0, #1 /* Clear M bit (MMU enable) */ + msr sctlr_el1, x0 + isb + /* Invalidate TLB for EL1 */ + tlbi vmalle1 + dsb sy + isb + b mmu_disabled
b reset?
arch/arm/mach-snapdragon/include/mach/boot0.h line 44
Quoted 11 lines
arch/arm/mach-snapdragon/include/mach/boot0.h +11
-0+disable_mmu_el3: +mrs x0, sctlr_el3 + bic x0, x0, #1 /* Clear M bit (MMU enable) */ + bic x0, x0, #(1 << 19) /* Clear WXN bit (Write XOR Execute) */ + msr sctlr_el3, x0 + isb + /* Invalidate entire TLB for all ELs */ + tlbi alle3 + dsb sy + isb + b mmu_disabled
b reset?
-Varada
Quoted 19 lines
arch/arm/mach-snapdragon/include/mach/boot0.h +12
-1+disable_mmu_el2: + mrs x0, sctlr_el2 + bic x0, x0, #1 /* Clear M bit (MMU enable) */ + msr sctlr_el2, x0 + isb + /* Invalidate TLB for EL2 */ + tlbi alle2 + dsb sy + isb +mmu_disabled: + b reset + #endif #endif --2.34.1
PATCH v2 4/6 soc: qcom: cmd-db: Allow boot without CMD DB data
In reply to Balaji SelvanathanIn snagboot mode, XBL loads U-Boot directly without populating CMD DB. The cmd-db driver fails to bind when CMD DB magic is invalid, blocking boot even when CMD DB is not strictly required.
Add QCOM_COMMAND_DB_OPTIONAL config to allow the driver to bind successfully when CMD DB data is absent. When enabled, a warning is logged and cmd_db_header is set to NULL, so consumer drivers receive errors on resource queries rather than preventing boot entirely.
---
Changes in v2:
- No changes
--- drivers/soc/qcom/Kconfig | 16 ++++++++++++++++ drivers/soc/qcom/cmd-db.c | 10 ++++++++++ 2 files changed, 26 insertions(+)
drivers/soc/qcom/Kconfig +16 -0
@@ -18,6 +18,22 @@ config QCOM_COMMAND_DB resource on a RPM-hardened platform must use this database to get SoC specific identifier and information for the shared resources. +config QCOM_COMMAND_DB_OPTIONAL + bool "Allow operation without Command DB data" + depends on QCOM_COMMAND_DB + help + Allow the Command DB driver to bind successfully even when CMD DB + data is not populated or has an invalid magic number. + + This is useful for platforms where CMD DB is not populated by + + When enabled, missing CMD DB will generate warnings but allow boot + to continue. Consumer drivers must handle cmd_db API failures + gracefully by checking return values. + + If unsure, say N. Most production Qualcomm platforms require + valid CMD DB data. + config QCOM_RPMH bool "Qualcomm RPMh support" depends on QCOM_COMMAND_DB
drivers/soc/qcom/cmd-db.c +10 -0
@@ -252,8 +252,18 @@ static int cmd_db_bind(struct udevice *dev) cmd_db_header = base;if (!cmd_db_magic_matches (cmd_db_header)) { +#ifdef CONFIG_QCOM_COMMAND_DB_OPTIONAL +log_warning ("%s: CMD DB magic not found (0x%02x%02x%02x%02x)\n" , + __func__, cmd_db_header->magic[0 ], cmd_db_header->magic[1 ], + cmd_db_header->magic[2 ], cmd_db_header->magic[3 ]); +log_warning ("%s: CMD DB data unavailable, resource queries will fail\n" , + __func__); + cmd_db_header =NULL ; +return 0 ; +#else log_err ("%s: Invalid Command DB Magic\n" , __func__);return -EINVAL ; +#endif }return 0 ;
Signature · 1 line
2.34.1
Re: [PATCH v2 4/6] soc: qcom: cmd-db: Allow boot without CMD DB data
Quoted 24 lines · Balaji Selvanathan
In snagboot mode, XBL loads U-Boot directly without populating CMD DB. The cmd-db driver fails to bind when CMD DB magic is invalid, blocking boot even when CMD DB is not strictly required.
Add
QCOM_COMMAND_DB_OPTIONALconfig to allow the driver to bind successfully when CMD DB data is absent. When enabled, a warning is logged andcmd_db_headeris set to NULL, so consumer drivers receive errors on resource queries rather than preventing boot entirely.Signed-off-by Balaji Selvanathan <[email protected]>---
Changes in v2:
- No changes--- drivers/soc/qcom/Kconfig | 16 ++++++++++++++++ drivers/soc/qcom/cmd-db.c | 10 ++++++++++ 2 files changed, 26 insertions(+)drivers/soc/qcom/Kconfig +0
-0@@ -18,6 +18,22 @@ config QCOM_COMMAND_DB resource on a RPM-hardened platform must use this database to get
drivers/soc/qcom/Kconfig config QCOM_COMMAND_DB · line 28
Quoted 10 lines
drivers/soc/qcom/Kconfig +8
-0SoC specific identifier and information for the shared resources. +config QCOM_COMMAND_DB_OPTIONAL + bool "Allow operation without Command DB data" + depends on QCOM_COMMAND_DB + help + Allow the Command DB driver to bind successfully even when CMD DB + data is not populated or has an invalid magic number. + + This is useful for platforms where CMD DB is not populated by
incomplete sentence?
-Varada
Quoted 38 lines
drivers/soc/qcom/Kconfig +8
-0+ + When enabled, missing CMD DB will generate warnings but allow boot + to continue. Consumer drivers must handle cmd_db API failures + gracefully by checking return values. + + If unsure, say N. Most production Qualcomm platforms require + valid CMD DB data. + config QCOM_RPMH bool "Qualcomm RPMh support" depends on QCOM_COMMAND_DBdrivers/soc/qcom/cmd-db.c +10
-1@@ -252,8 +252,18 @@ static int cmd_db_bind(struct udevice *dev) cmd_db_header = base;if (!cmd_db_magic_matches (cmd_db_header)) { +#ifdef CONFIG_QCOM_COMMAND_DB_OPTIONAL +log_warning ("%s: CMD DB magic not found (0x%02x%02x%02x%02x)\n" , + __func__, cmd_db_header->magic[0 ], cmd_db_header->magic[1 ], + cmd_db_header->magic[2 ], cmd_db_header->magic[3 ]); +log_warning ("%s: CMD DB data unavailable, resource queries will fail\n" , + __func__); + cmd_db_header =NULL ; +return 0 ; +#else log_err ("%s: Invalid Command DB Magic\n" , __func__);return -EINVAL ; +#endif }return 0 ; --2.34.1
PATCH v2 5/6 configs: add qcom_lemans_snagboot_defconfig for Lemans-EVK
In reply to Balaji SelvanathanAdd a defconfig for booting U-Boot in snagboot mode on Lemans-EVK development boards. In this mode, XBL loads U-Boot directly and U-Boot immediately enters fastboot over USB for partition flashing.
---
Changes in v2:
- Newly introduced in v2
--- configs/qcom_lemans_snagboot_defconfig | 49 ++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+)
configs/qcom_lemans_snagboot_defconfig new file +49 -0
@@ -0,0 +1,49 @@ +# Configuration for building U-Boot for snagboot/recovery mode +# on Lemans-EVK dev boards. +# +# For normal production boot, use qcom_lemans_defconfig instead. + +#include "qcom_defconfig" + +# Address where U-Boot will be loaded +CONFIG_TEXT_BASE=0x1c100000 +CONFIG_REMAKE_ELF=y +CONFIG_FASTBOOT_BUF_ADDR=0xdb300000 +CONFIG_DEFAULT_DEVICE_TREE="qcom/lemans-evk" +CONFIG_ENV_IS_IN_SCSI=y +CONFIG_ENV_SCSI_PART_USE_TYPE_GUID=y +# SCSI partition type GUID for logfs partition +CONFIG_ENV_SCSI_PART_TYPE_GUID="bc0330eb-3410-4951-a617-03898dbe3372" +# CONFIG_ENV_IS_DEFAULT is not set +# CONFIG_ENV_IS_NOWHERE is not set + +CONFIG_ENABLE_ARM_SOC_BOOT0_HOOK=y + +CONFIG_SKIP_RELOCATE=y + +CONFIG_FASTBOOT_FLASH_BLOCK=y +CONFIG_FASTBOOT_FLASH_BLOCK_INTERFACE_NAME="scsi" +CONFIG_FASTBOOT_FLASH_BLOCK_DEVICE_ID=4 +CONFIG_FASTBOOT_GPT_NAME="gpt" +CONFIG_FASTBOOT_MBR_NAME="mbr" + +# CONFIG_PSCI_RESET is not set + +CONFIG_COUNTER_FREQUENCY=19200000 + +# CONFIG_SAVE_PREV_BL_INITRAMFS_START_ADDR is not set + +# CONFIG_IOMMU is not set + +# CONFIG_REBOOT_MODE_ENV_UPDATE is not set + +CONFIG_QCOM_COMMAND_DB_OPTIONAL=y + +# Disable default env file to use CONFIG_BOOTCOMMAND instead +# This allows snagboot-specific bootcmd without modifying shared default.env +# CONFIG_ENV_USE_DEFAULT_ENV_TEXT_FILE is not set + +# Auto-enter fastboot mode for snagboot +CONFIG_USE_BOOTCOMMAND=y +CONFIG_BOOTCOMMAND="fastboot -l $fastboot_addr_r usb 0" +CONFIG_BOOTDELAY=0
Signature · 1 line
2.34.1
PATCH v2 6/6 MAINTAINERS: add qcom_lemans_snagboot_defconfig to ARM SNAPDRAGON
In reply to Balaji SelvanathanAdd an explicit file entry for the new Lemans-EVK snagboot defconfig to the ARM SNAPDRAGON section in MAINTAINERS.
---
Changes in v2:
- Newly introduced in v2
--- MAINTAINERS | 1 + 1 file changed, 1 insertion(+)
MAINTAINERS +1 -0
@@ -687,6 +687,7 @@ L: [email protected] S: Maintained T: git https://source.denx.de/u-boot/custodians/u-boot-snapdragon.git F: configs/qcm6490_defconfig +F: configs/qcom_lemans_snagboot_defconfig F: configs/qcs9100_defconfig F: drivers/*/*/pm8???-* F: drivers/gpio/msm_gpio.c
Signature · 1 line
2.34.1
Re: [PATCH v2 6/6] MAINTAINERS: add qcom_lemans_snagboot_defconfig to ARM SNAPDRAGON
Hiya,
Quoted 2 lines · Balaji Selvanathan
Add an explicit file entry for the new Lemans-EVK snagboot defconfig to the ARM SNAPDRAGON section in
MAINTAINERS.
You don't need this patch, the file is picked up by the "N: qcom" line
Quoted 22 lines
Signed-off-by Balaji Selvanathan <[email protected]>---
Changes in v2:
- Newly introduced in v2--- MAINTAINERS | 1 + 1 file changed, 1 insertion(+)MAINTAINERS +1
-0@@ -687,6 +687,7 @@ L: [email protected] S: Maintained T: git https://source.denx.de/u-boot/custodians/u-boot-snapdragon.git F: configs/qcm6490_defconfig +F: configs/qcom_lemans_snagboot_defconfig F: configs/qcs9100_defconfig F: drivers/*/*/pm8???-* F: drivers/gpio/msm_gpio.c
Signature · 1 line
// Casey (she/her)
Hi Balaji,
Quoted 7 lines · Balaji Selvanathan
This series adds support for running U-Boot in snagboot mode on Qualcomm Snapdragon platforms, targeting the Lemans-EVK board.
In snagboot mode, XBL loads U-Boot directly without initializing PSCI firmware or populating the Command DB. U-Boot then enters fastboot immediately, enabling partition flashing for manufacturing and recovery use cases.
Is this for building a firehose binary with U-Boot? Some additional explanation of what this is and why/how it should be used would be good.
Kind regards,
Quoted 54 lines
Patch 1 changes
SYSRESET_PSCIfrom 'select' to 'imply' so it can be disabled on platforms where PSCI firmware is unavailable.Patch 2 guards
show_psci_version()andqcom_psci_fixup()withCONFIG_ARM_SMCCCto prevent build failures when SMCCC is disabled.Patch 3 disables the MMU and invalidates TLBs at the earliest entry point to clear stale page tables left by previous bootloader before U-Boot sets up its own MMU.
Patch 4 adds
QCOM_COMMAND_DB_OPTIONALto allow the CMD DB driver to bind successfully when CMD DB data is not populated by XBL, logging a warning instead of failing.Patch 5 adds
qcom_lemans_snagboot_defconfigfor Lemans-EVK, based onqcom_defconfigwith snagboot-specific settings: SCSI-backed environment, optional CMD DB, PSCI reset disabled, and a bootcmd that auto-enters fastboot over USB with zero boot delay.Patch 6 adds the new defconfig to the ARM SNAPDRAGON section in
MAINTAINERS.Signed-off-by Balaji Selvanathan <[email protected]>---
Changes in v2:
- ChangedSYSRESET_PSCIfrom 'select' to 'imply'
- Guardshow_psci_version()andqcom_psci_fixup()withCONFIG_ARM_SMCCC
- Disables the MMU and invalidates TLBs at the earliest entry point
- Addqcom_lemans_snagboot_defconfigfor Lemans-EVK
- Link to v1: https://lore.kernel.org/u-boot/[email protected]/---
Balaji Selvanathan (6):
arm: snapdragon: MakeSYSRESET_PSCIoptional
arm: snapdragon: Guard PSCI functions withCONFIG_ARM_SMCCC
arm: snapdragon: Disable MMU early before U-Boot reset vector
soc: qcom: cmd-db: Allow boot without CMD DB data
configs: addqcom_lemans_snagboot_defconfigfor Lemans-EVK
MAINTAINERS: addqcom_lemans_snagboot_defconfigto ARM SNAPDRAGONMAINTAINERS | 1 + arch/arm/Kconfig | 2 +- arch/arm/mach-snapdragon/board.c | 14 ++++++++ arch/arm/mach-snapdragon/include/mach/boot0.h | 46 +++++++++++++++++++++++++ configs/qcom_lemans_snagboot_defconfig | 49 +++++++++++++++++++++++++++ drivers/soc/qcom/Kconfig | 16 +++++++++ drivers/soc/qcom/cmd-db.c | 10 ++++++ 7 files changed, 137 insertions(+), 1 deletion(-)---
base-commit:26fe27b4eaddcf73e4472368a71703a68e2f67d9
change-id: 20260608-snagboot-df4b6a79a086Best regards,
Signature · 1 line
// Casey (she/her)