[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090411001030.56e247c4@mjolnir.ossman.eu>
Date: Sat, 11 Apr 2009 00:10:30 +0200
From: Pierre Ossman <pierre@...man.eu>
To: Wolfgang Mües <wolfgang.mues@...rswald.de>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
"Matt Fleming" <matt@...sole-pimps.org>,
"David Brownell" <dbrownell@...rs.sourceforge.net>,
"Mike Frysinger" <vapier.adi@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mmc_spi: do propper retry managment in the block layer
On Wed, 8 Apr 2009 10:55:53 +0100
Wolfgang Mües <wolfgang.mues@...rswald.de> wrote:
> From: Wolfgang Muees <wolfgang.mues@...rswald.de>
>
> o This patch adds a propper retry managment for reading
> and writing data blocks for mmc and mmc_spi. Blocks are
> retransmitted 2 times in case of a transmission failure.
> This patch was tested with induced transmission errors
> by ESD pulses (and survived).
>
> Signed-off-by: Wolfgang Muees <wolfgang.mues@...rswald.de>
>
NAK. Writes cannot be retried safely as upper layers rely on the fact
that writes fail in a linear manner (a stupid assumption IMO, but
that's the way things are).
> + /* Invalid response. This is most likely a transmission
> + * error from card to host.
> + */
> + case -EINVAL:
EINVAL is actually "host controller driver/hardware does not support
this type of request".
Rgds
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists