Kconfig 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455
  1. # drivers/mtd/nand/Kconfig
  2. menuconfig MTD_NAND
  3. tristate "NAND Device Support"
  4. depends on MTD
  5. select MTD_NAND_IDS
  6. help
  7. This enables support for accessing all type of NAND flash
  8. devices. For further information see
  9. <http://www.linux-mtd.infradead.org/doc/nand.html>.
  10. if MTD_NAND
  11. config MTD_NAND_VERIFY_WRITE
  12. bool "Verify NAND page writes"
  13. help
  14. This adds an extra check when data is written to the flash. The
  15. NAND flash device internally checks only bits transitioning
  16. from 1 to 0. There is a rare possibility that even though the
  17. device thinks the write was successful, a bit could have been
  18. flipped accidentally due to device wear or something else.
  19. config MTD_NAND_ECC_SMC
  20. bool "NAND ECC Smart Media byte order"
  21. default n
  22. help
  23. Software ECC according to the Smart Media Specification.
  24. The original Linux implementation had byte 0 and 1 swapped.
  25. config MTD_NAND_MUSEUM_IDS
  26. bool "Enable chip ids for obsolete ancient NAND devices"
  27. depends on MTD_NAND
  28. default n
  29. help
  30. Enable this option only when your board has first generation
  31. NAND chips (page size 256 byte, erase size 4-8KiB). The IDs
  32. of these chips were reused by later, larger chips.
  33. config MTD_NAND_AUTCPU12
  34. tristate "SmartMediaCard on autronix autcpu12 board"
  35. depends on ARCH_AUTCPU12
  36. help
  37. This enables the driver for the autronix autcpu12 board to
  38. access the SmartMediaCard.
  39. config MTD_NAND_EDB7312
  40. tristate "Support for Cirrus Logic EBD7312 evaluation board"
  41. depends on ARCH_EDB7312
  42. help
  43. This enables the driver for the Cirrus Logic EBD7312 evaluation
  44. board to access the onboard NAND Flash.
  45. config MTD_NAND_H1900
  46. tristate "iPAQ H1900 flash"
  47. depends on ARCH_PXA && MTD_PARTITIONS
  48. help
  49. This enables the driver for the iPAQ h1900 flash.
  50. config MTD_NAND_GPIO
  51. tristate "GPIO NAND Flash driver"
  52. depends on GENERIC_GPIO && ARM
  53. help
  54. This enables a GPIO based NAND flash driver.
  55. config MTD_NAND_SPIA
  56. tristate "NAND Flash device on SPIA board"
  57. depends on ARCH_P720T
  58. help
  59. If you had to ask, you don't have one. Say 'N'.
  60. config MTD_NAND_AMS_DELTA
  61. tristate "NAND Flash device on Amstrad E3"
  62. depends on MACH_AMS_DELTA
  63. help
  64. Support for NAND flash on Amstrad E3 (Delta).
  65. config MTD_NAND_OMAP2
  66. tristate "NAND Flash device on OMAP2 and OMAP3"
  67. depends on ARM && MTD_NAND && (ARCH_OMAP2 || ARCH_OMAP3)
  68. help
  69. Support for NAND flash on Texas Instruments OMAP2 and OMAP3 platforms.
  70. config MTD_NAND_TS7250
  71. tristate "NAND Flash device on TS-7250 board"
  72. depends on MACH_TS72XX
  73. help
  74. Support for NAND flash on Technologic Systems TS-7250 platform.
  75. config MTD_NAND_IDS
  76. tristate
  77. config MTD_NAND_AU1550
  78. tristate "Au1550/1200 NAND support"
  79. depends on SOC_AU1200 || SOC_AU1550
  80. help
  81. This enables the driver for the NAND flash controller on the
  82. AMD/Alchemy 1550 SOC.
  83. config MTD_NAND_BF5XX
  84. tristate "Blackfin on-chip NAND Flash Controller driver"
  85. depends on (BF54x || BF52x) && MTD_NAND
  86. help
  87. This enables the Blackfin on-chip NAND flash controller
  88. No board specific support is done by this driver, each board
  89. must advertise a platform_device for the driver to attach.
  90. This driver can also be built as a module. If so, the module
  91. will be called bf5xx-nand.
  92. config MTD_NAND_BF5XX_HWECC
  93. bool "BF5XX NAND Hardware ECC"
  94. default y
  95. depends on MTD_NAND_BF5XX
  96. help
  97. Enable the use of the BF5XX's internal ECC generator when
  98. using NAND.
  99. config MTD_NAND_BF5XX_BOOTROM_ECC
  100. bool "Use Blackfin BootROM ECC Layout"
  101. default n
  102. depends on MTD_NAND_BF5XX_HWECC
  103. help
  104. If you wish to modify NAND pages and allow the Blackfin on-chip
  105. BootROM to boot from them, say Y here. This is only necessary
  106. if you are booting U-Boot out of NAND and you wish to update
  107. U-Boot from Linux' userspace. Otherwise, you should say N here.
  108. If unsure, say N.
  109. config MTD_NAND_RTC_FROM4
  110. tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
  111. depends on SH_SOLUTION_ENGINE
  112. select REED_SOLOMON
  113. select REED_SOLOMON_DEC8
  114. select BITREVERSE
  115. help
  116. This enables the driver for the Renesas Technology AG-AND
  117. flash interface board (FROM_BOARD4)
  118. config MTD_NAND_PPCHAMELEONEVB
  119. tristate "NAND Flash device on PPChameleonEVB board"
  120. depends on PPCHAMELEONEVB && BROKEN
  121. help
  122. This enables the NAND flash driver on the PPChameleon EVB Board.
  123. config MTD_NAND_S3C2410
  124. tristate "NAND Flash support for Samsung S3C SoCs"
  125. depends on ARCH_S3C2410 || ARCH_S3C64XX
  126. help
  127. This enables the NAND flash controller on the S3C24xx and S3C64xx
  128. SoCs
  129. No board specific support is done by this driver, each board
  130. must advertise a platform_device for the driver to attach.
  131. config MTD_NAND_S3C2410_DEBUG
  132. bool "Samsung S3C NAND driver debug"
  133. depends on MTD_NAND_S3C2410
  134. help
  135. Enable debugging of the S3C NAND driver
  136. config MTD_NAND_S3C2410_HWECC
  137. bool "Samsung S3C NAND Hardware ECC"
  138. depends on MTD_NAND_S3C2410
  139. help
  140. Enable the use of the controller's internal ECC generator when
  141. using NAND. Early versions of the chips have had problems with
  142. incorrect ECC generation, and if using these, the default of
  143. software ECC is preferable.
  144. config MTD_NAND_NDFC
  145. tristate "NDFC NanD Flash Controller"
  146. depends on 4xx
  147. select MTD_NAND_ECC_SMC
  148. help
  149. NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
  150. config MTD_NAND_S3C2410_CLKSTOP
  151. bool "Samsung S3C NAND IDLE clock stop"
  152. depends on MTD_NAND_S3C2410
  153. default n
  154. help
  155. Stop the clock to the NAND controller when there is no chip
  156. selected to save power. This will mean there is a small delay
  157. when the is NAND chip selected or released, but will save
  158. approximately 5mA of power when there is nothing happening.
  159. config MTD_NAND_DISKONCHIP
  160. tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
  161. depends on EXPERIMENTAL
  162. select REED_SOLOMON
  163. select REED_SOLOMON_DEC16
  164. help
  165. This is a reimplementation of M-Systems DiskOnChip 2000,
  166. Millennium and Millennium Plus as a standard NAND device driver,
  167. as opposed to the earlier self-contained MTD device drivers.
  168. This should enable, among other things, proper JFFS2 operation on
  169. these devices.
  170. config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
  171. bool "Advanced detection options for DiskOnChip"
  172. depends on MTD_NAND_DISKONCHIP
  173. help
  174. This option allows you to specify nonstandard address at which to
  175. probe for a DiskOnChip, or to change the detection options. You
  176. are unlikely to need any of this unless you are using LinuxBIOS.
  177. Say 'N'.
  178. config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
  179. hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
  180. depends on MTD_NAND_DISKONCHIP
  181. default "0"
  182. ---help---
  183. By default, the probe for DiskOnChip devices will look for a
  184. DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
  185. This option allows you to specify a single address at which to probe
  186. for the device, which is useful if you have other devices in that
  187. range which get upset when they are probed.
  188. (Note that on PowerPC, the normal probe will only check at
  189. 0xE4000000.)
  190. Normally, you should leave this set to zero, to allow the probe at
  191. the normal addresses.
  192. config MTD_NAND_DISKONCHIP_PROBE_HIGH
  193. bool "Probe high addresses"
  194. depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
  195. help
  196. By default, the probe for DiskOnChip devices will look for a
  197. DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
  198. This option changes to make it probe between 0xFFFC8000 and
  199. 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
  200. useful to you. Say 'N'.
  201. config MTD_NAND_DISKONCHIP_BBTWRITE
  202. bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
  203. depends on MTD_NAND_DISKONCHIP
  204. help
  205. On DiskOnChip devices shipped with the INFTL filesystem (Millennium
  206. and 2000 TSOP/Alon), Linux reserves some space at the end of the
  207. device for the Bad Block Table (BBT). If you have existing INFTL
  208. data on your device (created by non-Linux tools such as M-Systems'
  209. DOS drivers), your data might overlap the area Linux wants to use for
  210. the BBT. If this is a concern for you, leave this option disabled and
  211. Linux will not write BBT data into this area.
  212. The downside of leaving this option disabled is that if bad blocks
  213. are detected by Linux, they will not be recorded in the BBT, which
  214. could cause future problems.
  215. Once you enable this option, new filesystems (INFTL or others, created
  216. in Linux or other operating systems) will not use the reserved area.
  217. The only reason not to enable this option is to prevent damage to
  218. preexisting filesystems.
  219. Even if you leave this disabled, you can enable BBT writes at module
  220. load time (assuming you build diskonchip as a module) with the module
  221. parameter "inftl_bbt_write=1".
  222. config MTD_NAND_SHARPSL
  223. tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
  224. depends on ARCH_PXA
  225. config MTD_NAND_BASLER_EXCITE
  226. tristate "Support for NAND Flash on Basler eXcite"
  227. depends on BASLER_EXCITE
  228. help
  229. This enables the driver for the NAND flash device found on the
  230. Basler eXcite Smart Camera. If built as a module, the driver
  231. will be named excite_nandflash.
  232. config MTD_NAND_CAFE
  233. tristate "NAND support for OLPC CAFÉ chip"
  234. depends on PCI
  235. select REED_SOLOMON
  236. select REED_SOLOMON_DEC16
  237. help
  238. Use NAND flash attached to the CAFÉ chip designed for the OLPC
  239. laptop.
  240. config MTD_NAND_CS553X
  241. tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
  242. depends on X86_32
  243. help
  244. The CS553x companion chips for the AMD Geode processor
  245. include NAND flash controllers with built-in hardware ECC
  246. capabilities; enabling this option will allow you to use
  247. these. The driver will check the MSRs to verify that the
  248. controller is enabled for NAND, and currently requires that
  249. the controller be in MMIO mode.
  250. If you say "m", the module will be called cs553x_nand.
  251. config MTD_NAND_ATMEL
  252. tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
  253. depends on ARCH_AT91 || AVR32
  254. help
  255. Enables support for NAND Flash / Smart Media Card interface
  256. on Atmel AT91 and AVR32 processors.
  257. choice
  258. prompt "ECC management for NAND Flash / SmartMedia on AT91 / AVR32"
  259. depends on MTD_NAND_ATMEL
  260. config MTD_NAND_ATMEL_ECC_HW
  261. bool "Hardware ECC"
  262. depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9260 || AVR32
  263. help
  264. Use hardware ECC instead of software ECC when the chip
  265. supports it.
  266. The hardware ECC controller is capable of single bit error
  267. correction and 2-bit random detection per page.
  268. NB : hardware and software ECC schemes are incompatible.
  269. If you switch from one to another, you'll have to erase your
  270. mtd partition.
  271. If unsure, say Y
  272. config MTD_NAND_ATMEL_ECC_SOFT
  273. bool "Software ECC"
  274. help
  275. Use software ECC.
  276. NB : hardware and software ECC schemes are incompatible.
  277. If you switch from one to another, you'll have to erase your
  278. mtd partition.
  279. config MTD_NAND_ATMEL_ECC_NONE
  280. bool "No ECC (testing only, DANGEROUS)"
  281. depends on DEBUG_KERNEL
  282. help
  283. No ECC will be used.
  284. It's not a good idea and it should be reserved for testing
  285. purpose only.
  286. If unsure, say N
  287. endchoice
  288. endchoice
  289. config MTD_NAND_PXA3xx
  290. tristate "Support for NAND flash devices on PXA3xx"
  291. depends on MTD_NAND && PXA3xx
  292. help
  293. This enables the driver for the NAND flash device found on
  294. PXA3xx processors
  295. config MTD_NAND_PXA3xx_BUILTIN
  296. bool "Use builtin definitions for some NAND chips (deprecated)"
  297. depends on MTD_NAND_PXA3xx
  298. help
  299. This enables builtin definitions for some NAND chips. This
  300. is deprecated in favor of platform specific data.
  301. config MTD_NAND_CM_X270
  302. tristate "Support for NAND Flash on CM-X270 modules"
  303. depends on MTD_NAND && MACH_ARMCORE
  304. config MTD_NAND_PASEMI
  305. tristate "NAND support for PA Semi PWRficient"
  306. depends on MTD_NAND && PPC_PASEMI
  307. help
  308. Enables support for NAND Flash interface on PA Semi PWRficient
  309. based boards
  310. config MTD_NAND_TMIO
  311. tristate "NAND Flash device on Toshiba Mobile IO Controller"
  312. depends on MTD_NAND && MFD_TMIO
  313. help
  314. Support for NAND flash connected to a Toshiba Mobile IO
  315. Controller in some PDAs, including the Sharp SL6000x.
  316. config MTD_NAND_NANDSIM
  317. tristate "Support for NAND Flash Simulator"
  318. depends on MTD_PARTITIONS
  319. help
  320. The simulator may simulate various NAND flash chips for the
  321. MTD nand layer.
  322. config MTD_NAND_PLATFORM
  323. tristate "Support for generic platform NAND driver"
  324. depends on MTD_NAND
  325. help
  326. This implements a generic NAND driver for on-SOC platform
  327. devices. You will need to provide platform-specific functions
  328. via platform_data.
  329. config MTD_ALAUDA
  330. tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
  331. depends on MTD_NAND && USB
  332. help
  333. These two (and possibly other) Alauda-based cardreaders for
  334. SmartMedia and xD allow raw flash access.
  335. config MTD_NAND_ORION
  336. tristate "NAND Flash support for Marvell Orion SoC"
  337. depends on PLAT_ORION && MTD_NAND
  338. help
  339. This enables the NAND flash controller on Orion machines.
  340. No board specific support is done by this driver, each board
  341. must advertise a platform_device for the driver to attach.
  342. config MTD_NAND_FSL_ELBC
  343. tristate "NAND support for Freescale eLBC controllers"
  344. depends on MTD_NAND && PPC_OF
  345. help
  346. Various Freescale chips, including the 8313, include a NAND Flash
  347. Controller Module with built-in hardware ECC capabilities.
  348. Enabling this option will enable you to use this to control
  349. external NAND devices.
  350. config MTD_NAND_FSL_UPM
  351. tristate "Support for NAND on Freescale UPM"
  352. depends on MTD_NAND && (PPC_83xx || PPC_85xx)
  353. select FSL_LBC
  354. help
  355. Enables support for NAND Flash chips wired onto Freescale PowerPC
  356. processor localbus with User-Programmable Machine support.
  357. config MTD_NAND_MXC
  358. tristate "MXC NAND support"
  359. depends on ARCH_MX2 || ARCH_MX3
  360. help
  361. This enables the driver for the NAND flash controller on the
  362. MXC processors.
  363. config MTD_NAND_SH_FLCTL
  364. tristate "Support for NAND on Renesas SuperH FLCTL"
  365. depends on MTD_NAND && SUPERH && CPU_SUBTYPE_SH7723
  366. help
  367. Several Renesas SuperH CPU has FLCTL. This option enables support
  368. for NAND Flash using FLCTL. This driver support SH7723.
  369. config MTD_NAND_DAVINCI
  370. tristate "Support NAND on DaVinci SoC"
  371. depends on ARCH_DAVINCI
  372. help
  373. Enable the driver for NAND flash chips on Texas Instruments
  374. DaVinci processors.
  375. config MTD_NAND_TXX9NDFMC
  376. tristate "NAND Flash support for TXx9 SoC"
  377. depends on SOC_TX4938 || SOC_TX4939
  378. help
  379. This enables the NAND flash controller on the TXx9 SoCs.
  380. config MTD_NAND_SOCRATES
  381. tristate "Support for NAND on Socrates board"
  382. depends on MTD_NAND && SOCRATES
  383. help
  384. Enables support for NAND Flash chips wired onto Socrates board.
  385. endif # MTD_NAND