From: Bryan Wu <bryan.wu@analog.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: bryan.wu@analog.com, Thomas Gleixner <tglx@linutronix.de>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] Blackfin BF54x NAND Flash Controller driver
Date: Tue, 04 Sep 2007 01:33:49 +0800 [thread overview]
Message-ID: <1188840829.9063.10.camel@roc-laptop> (raw)
In-Reply-To: <1188837990.6075.32.camel@shinybook.infradead.org>
On Mon, 2007-09-03 at 17:46 +0100, David Woodhouse wrote:
> On Mon, 2007-09-03 at 15:25 +0800, Bryan Wu wrote:
> > + if (hardware_ecc) {
> > + if (plat->page_size == NFC_PG_SIZE_256) {
> > + chip->ecc.bytes = 3;
> > + chip->ecc.size = 256;
> > + } else if (mtd->writesize == NFC_PG_SIZE_512) {
>
> Comparing against plat->page_size in one case, but mtd->writesize in the
> other?
This is a typo in development. I will fix it ASAP. -:)
> And elsewhere it seems plat->page_size is treated as a boolean,
> indicating only 256-byte vs. 512-byte pages (you don't support 2KiB or
> other page sizes at all?)
>
When enabled hardware ECC, NFC of BF54x supports 256 and 512 bytes page
size ECC.
it's maybe little confusing with the NAND chip's pagesize. When NAND
chip is 2KiB or other page size, this driver can use multiple 256/512
pages to do hardware ECC. And it's handled by the driver software here.
-Bryan Wu
next prev parent reply other threads:[~2007-09-03 17:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 7:25 [PATCH] Blackfin BF54x NAND Flash Controller driver Bryan Wu
2007-09-03 10:14 ` Clemens Koller
2007-09-03 17:58 ` Mike Frysinger
2007-09-03 16:46 ` David Woodhouse
2007-09-03 17:33 ` Bryan Wu [this message]
2007-09-03 17:57 ` Mike Frysinger
2007-09-04 3:21 ` Bryan Wu
2007-09-13 8:37 ` Andrew Morton
2007-09-13 8:45 ` Mike Frysinger
2007-09-13 8:45 ` Bryan Wu
2007-09-13 8:51 ` Mike Frysinger
2007-09-13 8:49 ` Bryan Wu
2007-09-13 8:49 ` Andrew Morton
2007-09-14 7:19 ` Bryan Wu
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=1188840829.9063.10.camel@roc-laptop \
--to=bryan.wu@analog.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--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