diff options
| author | Igor Velkov <iav@iav.lv> | 2026-10-09 17:02:59 +0000 |
|---|---|---|
| committer | Ulf Hansson <ulfh@kernel.org> | 2026-11-05 18:56:25 +0100 |
| commit | 318fdb75f4dc9d18ae621b9fb25eb11160c95649 (patch) | |
| tree | 28ede8ca16068ca4d59fbf573256e000c6b2e2d3 /include/linux/timerqueue.h | |
| parent | 7e3cc541aa5855bc36e6cbffa82efc2795955a10 (diff) | |
mmc: meson-gx: report busy from DAT0 alone
meson_mmc_card_busy() reports busy only while DAT0..3 are all low. A
busy card drives DAT0 low and leaves DAT1..3 to the pull-ups, and the
callback is defined as "Check if the card is pulling dat[0] low". So a
busy card is reported free, and the core, which prefers card_busy over
CMD13 in mmc_busy_cb(), stops polling after CMD6 and erase at once. The
controller hides this on R1b commands, where it waits for busy itself.
Once max_busy_timeout is reported, the core sends the longer waits, the
120 s BKOPS and 240 s sanitize switches among them, as R1 and has only
the polling left.
Look at DAT0 only, as sdhci_card_busy() does. The checks around the
voltage switch in mmc_set_uhs_voltage() still hold: the card drives
DAT0..3 low together after CMD11 and keeps them low together on
failure.
Fixes: 186cd8b7f586 ("mmc: meson-gx: implement card_busy callback")
Cc: stable@vger.kernel.org
Signed-off-by: Igor Velkov <iav@iav.lv>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Signed-off-by: Ulf Hansson <ulfh@kernel.org>
Diffstat (limited to 'include/linux/timerqueue.h')
0 files changed, 0 insertions, 0 deletions
