Hi Jan, Thank you for the patch.
On Tue, Oct 06, 2026 at 11:27, Jan Kehren <[email protected]> wrote: > AVB assumed its partitions were on mmc: avb_ops_alloc() took a bare device > number and get_partition() called find_mmc_device(). bootmeth_android > accepts any bootdev but passes only desc->devnum, so an Android bootflow > found on nvme 0 or usb 0 is verified against mmc 0. > > Carry a uclass id alongside the device number and resolve the block device > with blk_get_devnum_by_uclass_id(), keeping mmc_init() and the hardware > partition switch on the mmc path only. "avb init <dev>" still means mmc, > "avb init <interface> <dev>" selects another bus, and both now look the > device up before allocating. get_boot_interface() returns UCLASS_INVALID > without ops, so a caller that skipped "avb init" fails rather than reading > mmc. > > Signed-off-by: Jan Kehren <[email protected]> Reviewed-by: Mattijs Korpershoek <[email protected]>
