Kconfig 14 KB

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