[PATCH] mtd: gpmi: properly handle bitflips in erased pages
boris.brezillon at free-electrons.com
Mon Dec 1 12:18:18 PST 2014
On Mon, 1 Dec 2014 11:41:39 -0800
Brian Norris <computersforpeace at gmail.com> wrote:
> Hi Boris,
> On Mon, Dec 01, 2014 at 08:12:39PM +0100, Boris Brezillon wrote:
> > Brian, I really like the idea of having a generic implementation for this
> > feature (using read_page_raw) as you suggested here , but this implies
> > having a temporary buffer to store the page read in raw mode and keep the page
> > read in normal (HW ECC engine eanbled) mode, and I'm not sure we want to
> > allocate more buffers than we already have.
> Why does this require an additional buffer? If we've already noticed an
> ECC error, we're expected to return raw data anyway, so what's the
> problem with clobbering the original data with a raw version of the
Well in the GPMI particular case (and more generally all NAND
controllers which do not support subpage write) this is true, but if you
can do subpage write, then you might have a bit flip in a specific
chunk which is still empty, while other chunks are written and are
expecting standard ECC correction.
In this case you want to keep the 3 chunks with standard ECC correction
and only one in raw mode with 'erased page bitflips' fixed.
> I really *really* do not want to merge another one-off attempt at
> "solving" this problem in the low-level driver, if at all possible.
We're definitely on the same page, this is why I asked some feedback.
> P.S. Sorry for not following up on my last attempt of a generic
> solution. I don't think I got enough constructive feedback, other than
> "this does not work for me", so I didn't pursue it further. If we have
> the attention of more than one driver developer here (i.e., at least you
> and me), then I'd really like to finish this off for good (?).
No problem, I can help you achieve this goal ;-).
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
More information about the linux-arm-kernel