On Thu, Sep 21, 2017 at 04:29:57PM +0200, Jean-Jacques Hiblot wrote:
The SDcard startup process currently handles only 2 modes. To make it easier to add support for more modes, let's make the process more generic and use a list of the modes to try. The major functional change is that when a mode fails we try the next one. Not all modes are tried, only those supported by the card and the host.
Signed-off-by: Jean-Jacques Hiblot jjhiblot@ti.com Reviewed-by: Simon Glass sjg@chromium.org
This change broke mmc with the vexpress_ca15_tc2 target and qemu-system-arm -M vexpress-a15.
commit d0c221fe7336fc7d9ada57d96f4a8911a3aac041 Author: Jean-Jacques Hiblot jjhiblot@ti.com AuthorDate: Thu Sep 21 16:29:57 2017 +0200 Commit: Jaehoon Chung jh80.chung@samsung.com CommitDate: Fri Jan 12 18:11:04 2018 +0900
mmc: refactor SD startup to make it easier to support new modes
The SDcard startup process currently handles only 2 modes. To make it easier to add support for more modes, let's make the process more generic and use a list of the modes to try. The major functional change is that when a mode fails we try the next one. Not all modes are tried, only those supported by the card and the host.
Signed-off-by: Jean-Jacques Hiblot jjhiblot@ti.com Reviewed-by: Simon Glass sjg@chromium.org
with a build from master e24bd1e79e223aa89854c0be95a53e2d538144a5
U-Boot 2018.03-rc1-00185-g1e19c70639 (Feb 09 2018 - 11:31:54 +1300)
DRAM: 1 GiB WARNING: Caches not enabled Flash: 128 MiB MMC: MMC: 0 *** Warning - bad CRC, using default environment
In: serial Out: serial Err: serial Net: smc911x-0 Hit any key to stop autoboot: 0 => load mmc 0:1 ${ramdisk_addr} fdt.dtb unable to select a mode mmc_init: -524, time 23 unable to select a mode mmc_init: -524, time 22 ** Bad device mmc 0 ** => load mmc 0:1 ${loadaddr} efi/boot/bootarm.efi unable to select a mode mmc_init: -524, time 21 unable to select a mode mmc_init: -524, time 21 ** Bad device mmc 0 ** => bootefi ${loadaddr} ${ramdisk_addr} ## Starting EFI application at a0008000 ... WARNING: using memory device/image path, this may confuse some payloads! Scanning disks on mmc... unable to select a mode mmc_init: -524, time 21 MMC Device 1 not found MMC Device 2 not found MMC Device 3 not found Found 0 disks WARNING: Invalid device tree, expect boot to fail efi_load_pe: Invalid DOS Signature