[PATCH] qcom_defconfig: Switch Qualcomm fastboot flash from MMC to block
Sumit Garg
sumit.garg at kernel.org
Fri May 1 09:54:42 CEST 2026
On Mon, Apr 27, 2026 at 10:29:39PM +0530, Balaji Selvanathan wrote:
>
> On 2/20/2026 2:39 PM, Sumit Garg wrote:
> > Hi Balaji,
> >
> > On Mon, Feb 16, 2026 at 09:45:49PM +0530, Balaji Selvanathan wrote:
> > > Replace MMC-specific fastboot flash configuration with generic
> > > block device support for Qualcomm platforms. This change switches
> > > from MMC device 0 to SCSI interface with device ID 4, enabling
> > > fastboot operations on UFS storage instead of eMMC.
> > I don't think if it's right for qcom generic defconfig to hardcode
> > fastboot flash device. Can you try to see rather if the fastboot flash
> > device can be determined at runtime? As otherwise it might end up in
> > target specific defconfig which we should avoid if we can.
>
> Hi Sumit,
>
> Implemented the runtime determination of fastboot device in : https://lore.kernel.org/u-boot/20260427-fb_gpt-v2-0-9e7fe3c1649a@oss.qualcomm.com/
>
> However, I think we need to assign CONFIG_FASTBOOT_FLASH_BLOCK_DEVICE_ID, so
> that if user doesnt provide device number in the fastboot commands, then we
> can use the device mentioned in CONFIG_FASTBOOT_FLASH_BLOCK_DEVICE_ID as
> default.
Please capture any patch-set dependencies in the comments section. I
think for this patch it would rather makes sense if you bundle it along
that fastboot patch-set.
-Sumit
More information about the U-Boot
mailing list