Kconfig 16 KB

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