From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd: nand: pass page number to ecc->write_xxx() methods
Date: Thu, 1 Oct 2015 20:13:22 +0200 [thread overview]
Message-ID: <20151001201322.5bc2cfe1@bbrezillon> (raw)
In-Reply-To: <20151001171750.GR143959@google.com>
On Thu, 1 Oct 2015 10:17:50 -0700
Brian Norris <computersforpeace@gmail.com> wrote:
> On Mon, Aug 24, 2015 at 07:10:19PM +0200, Boris Brezillon wrote:
> > The ->read_xxx() methods are all passed the page number the NAND controller
> > is supposed to read, but ->write_xxx() do not have such a parameter.
> >
> > This is a problem if we want to properly implement data
> > scrambling/randomization in order to mitigate MLC sensibility to repeated
> > pattern: to prevent bitflips in adjacent pages in the same block we need
> > to avoid repeating the same pattern at the same offset in those pages,
> > hence the randomizer/scrambler engine need to be passed the page value
> > in order to adapt its seed accordingly.
> >
> > Moreover, adding the page parameter the ->write_xxx() methods add some
> > consistency to the current model.
> >
> > Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> > CC: Josh Wu <josh.wu@atmel.com>
> > CC: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> > CC: Maxime Ripard <maxime.ripard@free-electrons.com>
> > CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > CC: Huang Shijie <shijie.huang@intel.com>
> > CC: Bryan Wu <bryan.wu@analog.com>
> > CC: devel at driverdev.osuosl.org
> > CC: linux-arm-kernel at lists.infradead.org
> > CC: linux-kernel at vger.kernel.org
> >
> > ---
> > drivers/mtd/nand/atmel_nand.c | 6 ++++--
> > drivers/mtd/nand/bf5xx_nand.c | 3 ++-
> > drivers/mtd/nand/brcmnand/brcmnand.c | 4 ++--
> > drivers/mtd/nand/cafe_nand.c | 3 ++-
> > drivers/mtd/nand/denali.c | 5 +++--
> > drivers/mtd/nand/docg4.c | 4 ++--
> > drivers/mtd/nand/fsl_elbc_nand.c | 4 ++--
> > drivers/mtd/nand/fsl_ifc_nand.c | 2 +-
> > drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 6 +++---
> > drivers/mtd/nand/hisi504_nand.c | 3 ++-
> > drivers/mtd/nand/lpc32xx_mlc.c | 3 ++-
> > drivers/mtd/nand/lpc32xx_slc.c | 5 +++--
> > drivers/mtd/nand/nand_base.c | 31 ++++++++++++++++++---------
> > drivers/mtd/nand/omap2.c | 3 ++-
> > drivers/mtd/nand/pxa3xx_nand.c | 3 ++-
> > drivers/mtd/nand/sh_flctl.c | 3 ++-
> > drivers/mtd/nand/sunxi_nand.c | 5 +++--
> > drivers/staging/mt29f_spinand/mt29f_spinand.c | 3 ++-
> > include/linux/mtd/nand.h | 6 +++---
> > 19 files changed, 63 insertions(+), 39 deletions(-)
>
> Tip for rebasing -- I noticed one build failure for docg4:
>
> drivers/mtd/nand/docg4.c: In function ?docg4_block_markbad?:
> drivers/mtd/nand/docg4.c:1116:2: error: too few arguments to function ?docg4_write_page?
> drivers/mtd/nand/docg4.c:985:12: note: declared here
Fixed in v2, thanks for the pointer.
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2015-10-01 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 17:10 [PATCH] mtd: nand: pass page number to ecc->write_xxx() methods Boris Brezillon
2015-10-01 15:07 ` Boris Brezillon
2015-10-01 16:58 ` Brian Norris
2015-10-01 17:17 ` Brian Norris
2015-10-01 18:13 ` Boris Brezillon [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=20151001201322.5bc2cfe1@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).