Kconfig 13 KB

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