[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210204120547.15381-1-yann.gautier@foss.st.com>
Date: Thu, 4 Feb 2021 13:05:45 +0100
From: <yann.gautier@...s.st.com>
To: <ulf.hansson@...aro.org>
CC: <linux@...linux.org.uk>, <linus.walleij@...aro.org>,
<ludovic.barre@...s.st.com>, <per.forlin@...aro.org>,
<huyue2@...ong.com>, <wsa+renesas@...g-engineering.com>,
<vbadigan@...eaurora.org>, <adrian.hunter@...el.com>,
<p.zabel@...gutronix.de>, <marex@...x.de>, <swboyd@...omium.org>,
<linux-mmc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<yann.gautier@...s.st.com>
Subject: [PATCH 0/2] mmc: mmci/mmc_test: update mmc_erase management
From: Yann Gautier <yann.gautier@...s.st.com>
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 this change has only been tested
on STM32MP1 boards, as I don't have ux500 hardware.
The mmc_test should rely on the erase argument set in the framework,
when using MMC_ERASE command.
Yann Gautier (2):
mmc: mmci: enable MMC_CAP_NEED_RSP_BUSY
mmc: mmc_test: use erase_arg for mmc_erase command
drivers/mmc/core/mmc_test.c | 2 +-
drivers/mmc/host/mmci.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.17.1
Powered by blists - more mailing lists