From: Matthieu CASTET <matthieu.castet@parrot.com>
To: "katsuki.uwatoko@toshiba.co.jp" <katsuki.uwatoko@toshiba.co.jp>
Cc: "vikram186@gmail.com" <vikram186@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"dedekind1@gmail.com" <dedekind1@gmail.com>
Subject: Re: [PATCH v2] mtd: nand: support BENAND (Built-in ECC NAND)
Date: Thu, 21 Feb 2013 10:50:15 +0100 [thread overview]
Message-ID: <5125EDD7.40202@parrot.com> (raw)
In-Reply-To: <F3B6523425E7914AA6214ED358D820AF2674E3EA@TGXML341.toshiba.local>
katsuki.uwatoko@toshiba.co.jp a écrit :
> This enables support for BENAND, which is an SLC NAND flash solution
> with embedded error correction code (ECC), currently supports only
> 128bytes OOB type.
>
> In the read sequence, "status read command" is executed to check the
> ECC status after read data. If bitflips occur, these are
> automatically corrected by BENAND and the status indicates the result.
>
> The write sequence is the same as raw write and the ECC data are
> automatically written to OOB by BENAND.
>
> Signed-off-by: UWATOKO Katsuki <katsuki.uwatoko@toshiba.co.jp>
> + case NAND_ECC_BENAND:
> + if (!IS_ENABLED(CONFIG_MTD_NAND_BENAND)) {
> + pr_warn("CONFIG_MTD_BENAND not enabled\n");
> + BUG();
> + }
> +
> + chip->ecc.read_page = nand_read_page_benand;
> + chip->ecc.write_page = nand_write_page_raw;
> + chip->ecc.read_page_raw = nand_read_page_raw;
> + chip->ecc.write_page_raw = nand_write_page_raw;
> + chip->ecc.read_oob = nand_read_oob_std;
> + chip->ecc.write_oob = nand_write_oob_std;
> +
Do you have a way to disable internal ecc ?
If not read_page_raw and write_page_raw won't do what is expected :
- read without ecc correction
- write without writing ecc or write custom ecc
I don't know if it could cause some problem.
Matthieu
next prev parent reply other threads:[~2013-02-21 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 6:17 [PATCH v2] mtd: nand: support BENAND (Built-in ECC NAND) katsuki.uwatoko
2013-02-21 9:50 ` Matthieu CASTET [this message]
2013-02-22 6:23 ` katsuki.uwatoko
2013-02-25 9:06 ` Gupta, Pekon
2013-02-25 9:24 ` Matthieu CASTET
2013-02-25 9:38 ` Gupta, Pekon
2013-02-25 10:18 ` Ricard Wanderlof
2013-02-25 11:10 ` Matthieu CASTET
2013-02-25 11:35 ` Gupta, Pekon
2013-02-26 2:41 ` katsuki.uwatoko
2013-03-11 8:57 ` Artem Bityutskiy
2013-03-18 2:40 ` katsuki.uwatoko
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=5125EDD7.40202@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=dedekind1@gmail.com \
--cc=katsuki.uwatoko@toshiba.co.jp \
--cc=linux-mtd@lists.infradead.org \
--cc=vikram186@gmail.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 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.