mmc: block: improve logging of handling emmc timeouts

Add some logging to make it clear just how the emmc timeout
was handled.

Signed-off-by: Ken Sumrall <ksumrall@android.com>
[AmitP: cherry-picked this Android patch from aosp
        common kernel android-4.4]
Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>

1 files changed, 8 insertions, 2 deletions

diff --git a/drivers/mmc/card/block.c b/drivers/mmc/card/block.c
index 9ce679255775..5f2a3d69344f 100644
--- a/drivers/mmc/card/block.c
+++ b/drivers/mmc/card/block.c
@@ -948,16 +948,22 @@ static int mmc_blk_cmd_error(struct request *req, const char *name, int error,
                         req->rq_disk->disk_name, "timed out", name, status);
 
                 /* If the status cmd initially failed, retry the r/w cmd */
-                if (!status_valid)
+                if (!status_valid) {
+                        pr_err("%s: status not valid, retrying timeout\n",
+                                req->rq_disk->disk_name);
                         return ERR_RETRY;
+                }
 
                 /*
                  * If it was a r/w cmd crc error, or illegal command
                  * (eg, issued in wrong state) then retry - we should
                  * have corrected the state problem above.
                  */
-                if (status & (R1_COM_CRC_ERROR | R1_ILLEGAL_COMMAND))
+                if (status & (R1_COM_CRC_ERROR | R1_ILLEGAL_COMMAND)) {
+                        pr_err("%s: command error, retrying timeout\n",
+                                req->rq_disk->disk_name);
                         return ERR_RETRY;
+                }
 
                 /* Otherwise abort the command */
                 return ERR_ABORT;