From: David Brownell <david-b@pacbell.net>
To: linux-mtd@lists.infradead.org, dwmw2@infradead.org, tglx@linutronix.de
Cc: davinci-linux-open-source@linux.davincidsp.com,
akpm@linux-foundation.org, s-paulraj@ti.com
Subject: Re: [PATCH v2 2/3] NAND: Add new ECC mode - ECC_HW_OOB_FIRST
Date: Fri, 19 Jun 2009 00:25:37 -0700 [thread overview]
Message-ID: <200906190025.38056.david-b@pacbell.net> (raw)
In-Reply-To: <1245183797-11469-1-git-send-email-s-paulraj@ti.com>
On Tuesday 16 June 2009, s-paulraj@ti.com wrote:
> From: Sandeep Paulraj <s-paulraj@ti.com>
>
> The patch applies to linux-mtd GIT tree
>
> This patch adds the new mode NAND_ECC_HW_OOB_FIRST in the nand code to
> support 4-bit ECC on TI DaVinci devices with large page (up to 4K) NAND
> chips. This ECC mode is similar to NAND_ECC_HW, with the exception of
> read_page API that first reads the OOB area, reads the data in chunks, feeds
> the ECC from OOB area to the ECC hw engine and perform any correction on the
> data as per the ECC status reported by the engine.
>
> "ECC_HW_OOB_FIRST" name suggested by Thomas Gleixner
>
> Reviewed-by: David Brownell <dbrownell@users.sourceforge.net>
> Signed-off-by: Sneha Narnakaje <nsnehaprabha@ti.com>
> Signed-off-by: Sandeep Paulraj <s-paulraj@ti.com
MTD folk ... any responses?
I don't think patches #1 and #2 changed much since the previous post.
The only issue was with patch #3, where details of the OOB layout had
needed tweaking.
> ---
> drivers/mtd/nand/nand_base.c | 59 ++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 59 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
> index a738333..93bb8f3 100644
> --- a/drivers/mtd/nand/nand_base.c
> +++ b/drivers/mtd/nand/nand_base.c
> @@ -980,6 +980,54 @@ static int nand_read_page_hwecc(struct mtd_info *mtd, struct nand_chip *chip,
> }
>
> /**
> + * nand_read_page_hwecc_oob_first - [REPLACABLE] hw ecc, read oob first
> + * @mtd: mtd info structure
> + * @chip: nand chip info structure
> + * @buf: buffer to store read data
> + *
> + * Hardware ECC for large page chips, require OOB to be read first.
> + * For this ECC mode, the write_page method is re-used from ECC_HW.
> + * These methods read/write ECC from the OOB area, unlike the
> + * ECC_HW_SYNDROME support with multiple ECC steps, follows the
> + * "infix ECC" scheme and reads/writes ECC from the data area, by
> + * overwriting the NAND manufacturer bad block markings.
> + */
> +static int nand_read_page_hwecc_oob_first(struct mtd_info *mtd,
> + struct nand_chip *chip, uint8_t *buf, int page)
> +{
> + int i, eccsize = chip->ecc.size;
> + int eccbytes = chip->ecc.bytes;
> + int eccsteps = chip->ecc.steps;
> + uint8_t *p = buf;
> + uint8_t *ecc_code = chip->buffers->ecccode;
> + uint32_t *eccpos = chip->ecc.layout->eccpos;
> + uint8_t *ecc_calc = chip->buffers->ecccalc;
> +
> + /* Read the OOB area first */
> + chip->cmdfunc(mtd, NAND_CMD_READOOB, 0, page);
> + chip->read_buf(mtd, chip->oob_poi, mtd->oobsize);
> + chip->cmdfunc(mtd, NAND_CMD_READ0, 0, page);
> +
> + for (i = 0; i < chip->ecc.total; i++)
> + ecc_code[i] = chip->oob_poi[eccpos[i]];
> +
> + for (i = 0; eccsteps; eccsteps--, i += eccbytes, p += eccsize) {
> + int stat;
> +
> + chip->ecc.hwctl(mtd, NAND_ECC_READ);
> + chip->read_buf(mtd, p, eccsize);
> + chip->ecc.calculate(mtd, p, &ecc_calc[i]);
> +
> + stat = chip->ecc.correct(mtd, p, &ecc_code[i], NULL);
> + if (stat < 0)
> + mtd->ecc_stats.failed++;
> + else
> + mtd->ecc_stats.corrected += stat;
> + }
> + return 0;
> +}
> +
> +/**
> * nand_read_page_syndrome - [REPLACABLE] hardware ecc syndrom based page read
> * @mtd: mtd info structure
> * @chip: nand chip info structure
> @@ -2673,6 +2721,17 @@ int nand_scan_tail(struct mtd_info *mtd)
> */
>
> switch (chip->ecc.mode) {
> + case NAND_ECC_HW_OOB_FIRST:
> + /* Similar to NAND_ECC_HW, but a separate read_page handle */
> + if (!chip->ecc.calculate || !chip->ecc.correct ||
> + !chip->ecc.hwctl) {
> + printk(KERN_WARNING "No ECC functions supplied, "
> + "Hardware ECC not possible\n");
> + BUG();
> + }
> + if (!chip->ecc.read_page)
> + chip->ecc.read_page = nand_read_page_hwecc_oob_first;
> +
> case NAND_ECC_HW:
> /* Use standard hwecc read page function ? */
> if (!chip->ecc.read_page)
>
next prev parent reply other threads:[~2009-06-19 7:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 20:23 [PATCH v2 2/3] NAND: Add new ECC mode - ECC_HW_OOB_FIRST s-paulraj
2009-06-19 7:25 ` David Brownell [this message]
2009-06-22 8:21 ` Artem Bityutskiy
2009-06-25 14:27 ` Paulraj, Sandeep
2009-06-22 10:18 ` Vitaly Wool
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=200906190025.38056.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=s-paulraj@ti.com \
--cc=tglx@linutronix.de \
/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