public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Chris Ball <cjb@laptop.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-mmc@vger.kernel.org
Subject: [PATCH 0/3] Improve MMC error handling (3rd rev)
Date: Mon, 20 Jun 2011 20:09:45 +0100	[thread overview]
Message-ID: <20110620190945.GK26089@n2100.arm.linux.org.uk> (raw)

This is the third revision of my improvements to the MMC block
device error handling, which makes error handling more robust
and permits MMC/SD to continue working in the presence of
not-quite-perfect setups.

Without this, my Versatile Express tends to fail to mount its rootfs
on SD.  With this, it can successfully read and write data from the
card in the presence of FIFO overruns and underruns, and also sensibly
recover from command channel errors.

There is more to come, but this is the "safer" bits of the improvements.

 drivers/mmc/card/block.c |  279 ++++++++++++++++++++++++++++++++++-----------
 include/linux/mmc/mmc.h  |   10 ++
 2 files changed, 221 insertions(+), 68 deletions(-)


             reply	other threads:[~2011-06-20 19:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 19:09 Russell King - ARM Linux [this message]
2011-06-20 19:10 ` [PATCH 1/3] MMC: allow get_card_status() to return error status Russell King - ARM Linux
2011-06-20 19:10 ` [PATCH 2/3] MMC: improve error recovery from command channel errors Russell King - ARM Linux
2011-06-20 19:10 ` [PATCH 3/3] MMC: add checking of r/w command response Russell King - ARM Linux
2011-06-20 19:34 ` [PATCH 0/3] Improve MMC error handling (3rd rev) Linus Walleij
2011-06-21 13:38 ` Pawel Moll
2011-06-21 16:23 ` Chris Ball

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110620190945.GK26089@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=cjb@laptop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox