Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   <yann.gautier@foss.st.com>
To:     <ulf.hansson@linaro.org>
CC:     <linux@armlinux.org.uk>, <linus.walleij@linaro.org>,
        <ludovic.barre@foss.st.com>, <per.forlin@linaro.org>,
        <huyue2@yulong.com>, <wsa+renesas@sang-engineering.com>,
        <vbadigan@codeaurora.org>, <adrian.hunter@intel.com>,
        <p.zabel@pengutronix.de>, <marex@denx.de>, <swboyd@chromium.org>,
        <linux-mmc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <yann.gautier@foss.st.com>
Subject: [PATCH 0/2] mmc: mmci/mmc_test: update mmc_erase management
Date:   Thu, 4 Feb 2021 13:05:45 +0100
Message-ID: <20210204120547.15381-1-yann.gautier@foss.st.com>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

From: Yann Gautier <yann.gautier@foss.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