Skip to content

snagfactory: recognize 'ufs<num>' as a valid target-device - #5

Merged
BakyarajM merged 1 commit into
USB-timeoutfrom
UFS-support
Sep 2, 2026
Merged

BakyarajM merged 1 commit into
USB-timeoutfrom
UFS-support

Conversation

@BakyarajM

Copy link
Copy Markdown

UFS is LBA-addressable like eMMC, so accept 'ufs' as a target-device value and skip the eraseblk-size requirement for it, same as for 'mmc'.

However, U-Boot addresses UFS storage through the "scsi", rather than the "mmc"-specific commands generated by the "gpt", "flash", "mtd-parts" and "emmc-hwpart" tasks. Reject 'ufs' targets for these tasks with a clear configuration error pointing users to the "run" task, which can issue the equivalent raw commands directly (e.g. "oem_run:gpt write scsi ...").

Signed-off-by: Bakyaraj Moorthy bmoorthy@qti.qualcomm.com

@BakyarajM BakyarajM changed the title Ufs support snagfactory: recognize 'ufs<num>' as a valid target-device Sep 1, 2026
UFS is LBA-addressable like eMMC, so accept 'ufs' as
a target-device value and skip the eraseblk-size requirement for
it, same as for 'mmc<num>'.

However, U-Boot addresses UFS storage through the "scsi",
rather than the "mmc"-specific commands generated by the "gpt",
"flash", "mtd-parts" and "emmc-hwpart" tasks. Reject 'ufs'
targets for these tasks with a clear configuration error pointing
users to the "run" task, which can issue the equivalent raw commands
directly (e.g. "oem_run:gpt write scsi <dev> ...").

Signed-off-by: Bakyaraj Moorthy <bmoorthy@qti.qualcomm.com>
@BakyarajM
BakyarajM merged commit dd8cf65 into USB-timeout Sep 2, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants