Kconfig 19 KB

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