Kconfig 16 KB

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