Kconfig 16 KB

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