Kconfig 15 KB

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