Kconfig 19 KB

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