From: Troy Kisky <troy.kisky@boundarydevices.com>
To: nsnehaprabha@ti.com
Cc: dwmw2@infradead.org,
davinci-linux-open-source@linux.davincidsp.com,
linux-mtd@lists.infradead.org, tglx@linutronix.de,
akpm@linux-foundation.org
Subject: Re: [PATCH 2.6.30-rc6 3/3] NAND: Add 4-bit ECC support for large page NAND chips
Date: Mon, 18 May 2009 16:57:48 -0700 [thread overview]
Message-ID: <4A11F5FC.40709@boundarydevices.com> (raw)
In-Reply-To: <1242682705-19845-1-git-send-email-nsnehaprabha@ti.com>
nsnehaprabha@ti.com wrote:
> From: Sneha Narnakaje <nsnehaprabha@ti.com>
>
> This patch adds 4-bit ECC support for large page NAND chips using the new ECC
> mode NAND_ECC_HW_OOB_FIRST. The platform data from board-dm355-evm has been
> adjusted to use this mode.
>
> The patches have been verified on DM355 device with 2K Micron devices using
> mtd-tests and JFFS2. Error correction upto 4-bits has also been verified using
> nandwrite/nanddump utilities.
>
> Reviewed-by: David Brownell <dbrownell@users.sourceforge.net>
> Signed-off-by: Sneha Narnakaje <nsnehaprabha@ti.com>
> ---
> drivers/mtd/nand/davinci_nand.c | 37 +++++++++++++++++++++++++++++++------
> 1 files changed, 31 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/mtd/nand/davinci_nand.c b/drivers/mtd/nand/davinci_nand.c
> index ba6940d..4557b8d 100644
> --- a/drivers/mtd/nand/davinci_nand.c
> +++ b/drivers/mtd/nand/davinci_nand.c
> @@ -500,6 +500,24 @@ static struct nand_ecclayout hwecc4_small __initconst = {
> },
> };
>
> +/* An ECC layout for using 4-bit ECC with large-page (2048bytes) flash,
> + * storing ten ECC bytes plus the manufacturer's bad block marker byte,
> + * and not overlapping the default BBT markers.
> + */
> +static struct nand_ecclayout hwecc4_2048 __initconst = {
> + .eccbytes = 40,
> + .eccpos = { 0, 1, 2, 3, 4,
> + /* offset 5 holds the badblock marker */
I don't see any bad block overrides to move it from bytes 0,1
to byte 5 in this patch. What am I missing?
> + 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
> + /* 8 bytes at offset 16 hold JFFS2 clean markers */
> + 24, 25, 26, 27, 28,
> + 29, 30, 31, 32, 33, 34, 35, 36, 37, 38,
> + 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, },
> + .oobfree = {
> + {.offset = 16, .length = 8, },
> + {.offset = 49, },
> + },
> +};
>
> static int __init nand_davinci_probe(struct platform_device *pdev)
> {
> @@ -689,15 +707,22 @@ static int __init nand_davinci_probe(struct platform_device *pdev)
> info->mtd.oobsize - 16;
> goto syndrome_done;
> }
> + if (chunks == 4) {
> + info->ecclayout = hwecc4_2048;
> + info->ecclayout.oobfree[1].length =
> + info->mtd.oobsize - 49;
- info->ecclayout.oobfree[1].offset instead of 49 would look better.
or move the .offset = 49 here too.
> + info->chip.ecc.mode = NAND_ECC_HW_OOB_FIRST;
> + goto syndrome_done;
> + }
>
> - /* For large page chips we'll be wanting to use a
> - * not-yet-implemented mode that reads OOB data
> - * before reading the body of the page, to avoid
> - * the "infix OOB" model of NAND_ECC_HW_SYNDROME
> - * (and preserve manufacturer badblock markings).
> + /* 4K page chips are not yet supported. The eccpos from
> + * nand_ecclayout cannot hold 80bytes and change to eccpos[]
> + * breaks userspace ioctl interface with mtd-utils. Once we
> + * resolve this issue, NAND_ECC_HW_OOB_FIRST mode can be used
> + * for the 4K page chips.
> */
> dev_warn(&pdev->dev, "no 4-bit ECC support yet "
> - "for large page NAND\n");
> + "for 4K page NAND\n");
> ret = -EIO;
> goto err_scan;
>
next prev parent reply other threads:[~2009-05-18 23:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 21:38 [PATCH 2.6.30-rc6 3/3] NAND: Add 4-bit ECC support for large page NAND chips nsnehaprabha
2009-05-18 23:57 ` Troy Kisky [this message]
2009-05-19 0:17 ` Troy Kisky
2009-05-20 14:11 ` Narnakaje, Snehaprabha
2009-05-20 19:06 ` Troy Kisky
2009-05-20 19:18 ` Narnakaje, Snehaprabha
2009-05-20 20:18 ` Troy Kisky
2009-05-20 20:49 ` Narnakaje, Snehaprabha
2009-05-21 0:23 ` Troy Kisky
2009-05-20 14:06 ` Narnakaje, Snehaprabha
2009-05-21 0:38 ` David Brownell
2009-05-23 3:51 ` Narnakaje, Snehaprabha
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=4A11F5FC.40709@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=akpm@linux-foundation.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nsnehaprabha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.