diff options
author | Bryan Wu <bryan.wu@analog.com> | 2007-10-02 16:56:05 -0400 |
---|---|---|
committer | David Woodhouse <dwmw2@infradead.org> | 2007-10-13 09:36:49 -0400 |
commit | b37bde147890c8fea8369a5a4e230dabdea4ebfb (patch) | |
tree | b447c6b44d7c5b48ead3366db74654c7cc64a4d6 /drivers/mtd/nand/Kconfig | |
parent | c4a9f88daf6c382fedde4cdddef0b30f1d0a20db (diff) |
[MTD] [NAND] Blackfin on-chip NAND Flash Controller driver
This is the driver for latest Blackfin on-chip nand flash controller
- use nand_chip and mtd_info common nand driver interface
- provide both PIO and dma operation
- compiled with ezkit bf548 configuration
- use hardware 1-bit ECC
- tested with YAFFS2 and can mount YAFFS2 filesystem as rootfs
ChangeLog from try#1
- use hweight32() instead of count_bits()
- replace bf54x with bf5xx and BF54X with BF5XX
- compare against plat->page_size in 2 cases when enable hardware ECC
ChangeLog from try#2
- passed nand_test suites
- use cpu_relax() instead of busy wait loop
- some coding style issue pointed out by Andrew
Signed-off-by: Bryan Wu <bryan.wu@analog.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
Diffstat (limited to 'drivers/mtd/nand/Kconfig')
-rw-r--r-- | drivers/mtd/nand/Kconfig | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/drivers/mtd/nand/Kconfig b/drivers/mtd/nand/Kconfig index d3ec309f2435..8f9c3baeb38e 100644 --- a/drivers/mtd/nand/Kconfig +++ b/drivers/mtd/nand/Kconfig | |||
@@ -91,6 +91,25 @@ config MTD_NAND_AU1550 | |||
91 | This enables the driver for the NAND flash controller on the | 91 | This enables the driver for the NAND flash controller on the |
92 | AMD/Alchemy 1550 SOC. | 92 | AMD/Alchemy 1550 SOC. |
93 | 93 | ||
94 | config MTD_NAND_BF5XX | ||
95 | tristate "Blackfin on-chip NAND Flash Controller driver" | ||
96 | depends on BF54x && MTD_NAND | ||
97 | help | ||
98 | This enables the Blackfin on-chip NAND flash controller | ||
99 | |||
100 | No board specific support is done by this driver, each board | ||
101 | must advertise a platform_device for the driver to attach. | ||
102 | |||
103 | This driver can also be built as a module. If so, the module | ||
104 | will be called bf5xx-nand. | ||
105 | |||
106 | config MTD_NAND_BF5XX_HWECC | ||
107 | bool "BF5XX NAND Hardware ECC" | ||
108 | depends on MTD_NAND_BF5XX | ||
109 | help | ||
110 | Enable the use of the BF5XX's internal ECC generator when | ||
111 | using NAND. | ||
112 | |||
94 | config MTD_NAND_RTC_FROM4 | 113 | config MTD_NAND_RTC_FROM4 |
95 | tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)" | 114 | tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)" |
96 | depends on SH_SOLUTION_ENGINE | 115 | depends on SH_SOLUTION_ENGINE |