Kconfig 13 KB

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