Kconfig 19 KB

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