[PATCH v2025.09.y 04/58] mci: am654-sdhci: Wait for transfer complete interrupt with MMC_RSP_BUSY cmd
Ahmad Fatoum
a.fatoum at pengutronix.de
Fri Mar 13 06:24:48 PDT 2026
From: Sascha Hauer <s.hauer at pengutronix.de>
The MMC_RSP_BUSY flag indicates that we have to wait for the transfer
completion interrupt. Other SDHCI drivers do this, but the am654 driver
missed it.
(cherry picked from commit 0b7c6416b9684a2c304cf18366c5feb3b4a38867)
Link: https://lore.barebox.org/20250828113442.3543907-1-s.hauer@pengutronix.de
Signed-off-by: Sascha Hauer <s.hauer at pengutronix.de>
---
drivers/mci/am654-sdhci.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/mci/am654-sdhci.c b/drivers/mci/am654-sdhci.c
index bb67c8bf4693..4ceea226f717 100644
--- a/drivers/mci/am654-sdhci.c
+++ b/drivers/mci/am654-sdhci.c
@@ -458,7 +458,7 @@ static int am654_sdhci_send_cmd(struct mci_host *mci, struct mci_cmd *cmd,
struct mci_data *data)
{
struct am654_sdhci_plat *host = container_of(mci, struct am654_sdhci_plat, mci);
- u32 command, xfer;
+ u32 mask, command, xfer;
int ret;
dma_addr_t dma;
@@ -468,6 +468,10 @@ static int am654_sdhci_send_cmd(struct mci_host *mci, struct mci_cmd *cmd,
sdhci_write32(&host->sdhci, SDHCI_INT_STATUS, ~0);
+ mask = SDHCI_INT_CMD_COMPLETE;
+ if (cmd->resp_type & MMC_RSP_BUSY)
+ mask |= SDHCI_INT_XFER_COMPLETE;
+
sdhci_write8(&host->sdhci, SDHCI_TIMEOUT_CONTROL, 0xe);
sdhci_setup_data_dma(&host->sdhci, data, &dma);
@@ -480,7 +484,7 @@ static int am654_sdhci_send_cmd(struct mci_host *mci, struct mci_cmd *cmd,
sdhci_write32(&host->sdhci, SDHCI_ARGUMENT, cmd->cmdarg);
sdhci_write16(&host->sdhci, SDHCI_COMMAND, command);
- ret = sdhci_wait_for_done(&host->sdhci, SDHCI_INT_CMD_COMPLETE);
+ ret = sdhci_wait_for_done(&host->sdhci, mask);
if (ret) {
sdhci_teardown_data(&host->sdhci, data, dma);
goto error;
--
2.47.3
More information about the barebox
mailing list