Kconfig 18 KB

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