lkml.org 
[lkml]   [2009]   [May]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] mmc_spi: use EILSEQ for possible transmission errors
On Wed, 20 May 2009 02:20:46 -0700
David Brownell <david-b@pacbell.net> wrote:

> On Wednesday 20 May 2009, Wolfgang Mües wrote:
> > R1_SPI_COM_CRC is a transmission error - no doubt. Mapping to EILSEQ is OK.
> >
> > R1_SPI_ERASE_SEQ and R1_SPI_ERASE_RESET are responses to a sector erase
> > command. block.c is not sending such commands, so block.c can safely assume
> > that each such response is a transmission error.
>
> Hmm, would hope that's not a long-term plan. Remember that the
> firmware in the card can leverage "that's erased" knowledge for
> things like wear leveling. SSDs and other storage devices would
> likewise benefit from such knowledge. I'm quite certain there's
> been discussion about adding support for that in the block layer.
>

It's already in AFAIK. I even had code for hooking it up to mmc_block.
But it didn't produce any measurable results so I never merged it.

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.
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2009-05-20 12:11    [W:0.903 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site