linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Boris Brezillon <boris.brezillon@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Marek Vasut <marek.vasut@gmail.com>
Cc: linux-mtd@lists.infradead.org,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Antoine Tenart <antoine.tenart@bootlin.com>,
	Gregory Clement <gregory.clement@bootlin.com>,
	Maxime Chevallier <maxime.chevallier@bootlin.com>,
	Nadav Haklai <nadavh@marvell.com>,
	Ofer Heifetz <oferh@marvell.com>
Subject: Re: [PATCH 0/3] mtd: rawnand: marvell: add new layout
Date: Thu, 6 Sep 2018 22:10:58 +0200	[thread overview]
Message-ID: <20180906221058.338f8c43@xps13> (raw)
In-Reply-To: <20180719152337.6372-1-miquel.raynal@bootlin.com>

Hello,

Miquel Raynal <miquel.raynal@bootlin.com> wrote on Thu, 19 Jul 2018
17:23:34 +0200:

> Hello,
> 
> This series is an attempt at supporting a new layout for Marvell NAND
> controller: NAND chips using 2kiB pages, requesting at least 8
> correctable bits per 512-byte chunks.
> 
> While this could have been trivial by the simple addition of this
> layout in the marvell_nfc_layout table as described in Marvell (not
> public) AN-379, actual testing shown a strange error. With this
> layout, one bitflip appears on the second chunk of every erased page
> when we read with BCH ECC engine activated.
> 
> It has been experimentally checked that using 64 free OOB bytes
> instead of 32 in the second chunk cancels this bitflip. However, this
> is not a viable solution as the BootROM would not find the ECC bytes
> at the right place and would declare bad any block written with this
> layout.
> 
> The solution found was to re-read in raw mode the whole page instead
> of just the ECC bytes when an ECC error occurs to check if the entire
> page is empty or not.
> 
> Also, with this layout, Bad Block Markers (BBM) are expected to be
> within the data area. Prevent any use of the BBM in this case.
> 
> The first patch reworks the ECC failure path of the BCH read function,
> the second patch adds support for the new layout with the above
> problems addressed and the last patch is just an optimization of the
> same ECC failure path for the Hamming read function.
> 
> Thanks,
> Miquèl
> 
> 
> Miquel Raynal (3):
>   mtd: rawnand: marvell: rework BCH engine failure path
>   mtd: rawnand: marvell: support 8b/512B strength for 2kiB pages layout
>   mtd: rawnand: marvell: speed-up hamming failure path
> 
>  drivers/mtd/nand/raw/marvell_nand.c | 123 +++++++++++++++++++++++-------------
>  1 file changed, 79 insertions(+), 44 deletions(-)
> 

Patches 1 and 2 applied, patch 3 dropped because it would have cause
pxa (NFCv1) not to work anymore because of the unsupported "change
column".

Thanks,
Miquèl

      parent reply	other threads:[~2018-09-06 20:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 15:23 [PATCH 0/3] mtd: rawnand: marvell: add new layout Miquel Raynal
2018-07-19 15:23 ` [PATCH 1/3] mtd: rawnand: marvell: rework BCH engine failure path Miquel Raynal
2018-07-19 15:23 ` [PATCH 2/3] mtd: rawnand: marvell: support 8b/512B strength for 2kiB pages layout Miquel Raynal
2018-07-19 15:23 ` [PATCH 3/3] mtd: rawnand: marvell: speed-up hamming failure path Miquel Raynal
2018-09-06 12:37 ` [PATCH 0/3] mtd: rawnand: marvell: add new layout Boris Brezillon
2018-09-06 20:10 ` Miquel Raynal [this message]

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=20180906221058.338f8c43@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=antoine.tenart@bootlin.com \
    --cc=boris.brezillon@bootlin.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=gregory.clement@bootlin.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=nadavh@marvell.com \
    --cc=oferh@marvell.com \
    --cc=richard@nod.at \
    --cc=thomas.petazzoni@bootlin.com \
    /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;
as well as URLs for NNTP newsgroup(s).