Kconfig 18 KB

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