From: Bryan Wu <bryan.wu@analog.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: bryan.wu@analog.com, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org,
Thomas Gleixner <tglx@linutronix.de>,
David Woodhouse <dwmw2@infradead.org>,
akpm@linux-foundation.org
Subject: Re: [PATCH] Blackfin BF54x NAND Flash Controller driver
Date: Tue, 04 Sep 2007 11:21:49 +0800 [thread overview]
Message-ID: <1188876109.6319.9.camel@roc-desktop> (raw)
In-Reply-To: <8bd0f97a0709031057u1f4608f6y36bd20a8f6910a32@mail.gmail.com>
On Mon, 2007-09-03 at 13:57 -0400, Mike Frysinger wrote:
> On 9/3/07, Bryan Wu <bryan.wu@analog.com> wrote:
> > --- a/drivers/mtd/nand/Kconfig
> > +++ b/drivers/mtd/nand/Kconfig
> > @@ -131,6 +131,24 @@ config MTD_NAND_AU1550
> > +config MTD_NAND_BF54X
> > + tristate "NAND Flash support for Blackfin BF54X SoC DSP"
>
> i'd just describe it as "Blackfin on-chip NAND" rather than sticking
> in exact part numbers as i imagine we can extend it down the line
>
> > + This enables the NAND flash controller on the BF54X SoC DPSs
>
> "BF54X SoC DPSs" -> "BF54x SoC DSPs"
>
> > + No board specific support is done by this driver, each board
> > + must advertise a platform_device for the driver to attach.
>
> should mention the module name when built as a module
>
I will get rid of this BF54X and use BF5XX for (BF54x and BF52x and
future processor)
> > +config MTD_NAND_BF54X_HWECC
> > + bool "BF54X NAND Hardware ECC"
> > + depends on MTD_NAND_BF54X
> > + help
> > + Enable the use of the BF54X's internal ECC generator when
> > + using NAND. Early versions of the chip have had problems with
> > + incorrect ECC generation, and if using these, the default of
> > + software ECC is preferable.
>
> rather than advertising this, i'd just keep it in the driver ...
> presumably there are anomaly #'s for when the ECC is wrong, so we can
> make the code depend on those
> -mike
This option is quite common in the NAND driver. If there are anomaly
#'s, code can still depend on those by using hardware_ecc varible. This
option is very useful when someone need software_ecc.
Thanks
- Bryan Wu
next prev parent reply other threads:[~2007-09-04 3:24 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
2007-09-03 17:57 ` Mike Frysinger
2007-09-04 3:21 ` Bryan Wu [this message]
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=1188876109.6319.9.camel@roc-desktop \
--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 \
--cc=vapier.adi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox