summaryrefslogtreecommitdiffstats
path: root/drivers/mmc/core/mmc_ops.h
diff options
context:
space:
mode:
authorUlf Hansson <ulf.hansson@linaro.org>2016-11-21 15:49:48 +0100
committerUlf Hansson <ulf.hansson@linaro.org>2016-11-29 09:05:24 +0100
commit5ec32f84111a500c142961c82dd415c22e64e2be (patch)
tree31c5194aa219d6ae645275bf8bdffd6ed6ba5ac1 /drivers/mmc/core/mmc_ops.h
parent625228fa3e017d80f547b35214c60b4081b5c07d (diff)
downloadop-kernel-dev-5ec32f84111a500c142961c82dd415c22e64e2be.zip
op-kernel-dev-5ec32f84111a500c142961c82dd415c22e64e2be.tar.gz
mmc: core: Check SWITCH_ERROR bit from each CMD13 response when polling
According to the JEDEC specification, the SWITCH_ERROR bit in the device status from a R1 response, is an error bit which may be cleared as soon as the response that reports the error is sent. When polling with CMD13 to find out when the card stops signaling busy after a CMD6 has been sent, we currently parse only the last CMD13 response for the SWITCH_ERROR bit. Consequentially we could loose important information about the card. In worst case if the card stops signaling busy within the allowed timeout, we could end up believing that the CMD6 command completed successfully, when in fact it didn't. To improve the behaviour, let's parse each CMD13 response to see if the SWITCH_ERROR bit is set in the device status. In such case, we abort the polling loop and report the error. Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Tested-by: Linus Walleij <linus.walleij@linaro.org> Acked-by: Adrian Hunter <adrian.hunter@intel.com>
Diffstat (limited to 'drivers/mmc/core/mmc_ops.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud