[PATCH v2] mmc: mmc_test: use erase_arg for mmc_erase command

From: Yann Gautier Since [1], the erase argument for mmc_erase() function is saved in erase_arg field of card structure. It is preferable to use it instead of hard-coded MMC_SECURE_ERASE_ARG, which from eMMC 4.51 spec is not recommended: "6.6.16 Secure Erase NOTE Secure Erase is included for back

[PATCH 1/2] mmc: mmci: enable MMC_CAP_NEED_RSP_BUSY

From: Yann Gautier To properly manage commands awaiting R1B responses, the capability MMC_CAP_NEED_RSP_BUSY is enabled in mmci driver, for variants that manage busy detection. This R1B management needs both the flags MMC_CAP_NEED_RSP_BUSY and MMC_CAP_WAIT_WHILE_BUSY to be enabled together. Signe

[PATCH 2/2] mmc: mmc_test: use erase_arg for mmc_erase command

From: Yann Gautier Since [1], the erase argument for mmc_erase() function is saved in erase_arg field of card structure. It is preferable to use it instead of hard-coded MMC_SECURE_ERASE_ARG, which from eMMC 4.51 spec is not recommended: "6.6.16 Secure Erase NOTE Secure Erase is included for back

[PATCH 0/2] mmc: mmci/mmc_test: update mmc_erase management

From: Yann Gautier We are facing issues when testing STM32MP157C-EV1 board with latest MMC developments. The commands with R1B responses weren't correctly managed, needing MMC_CAP_NEED_RSP_BUSY. The Ux500 platforms have the same busy detection feature, so this flag is enabled for them too. But t