Kconfig 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563
  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_ECC
  14. help
  15. This enables support for accessing all type of NAND flash
  16. devices. For further information see
  17. <http://www.linux-mtd.infradead.org/doc/nand.html>.
  18. if MTD_NAND
  19. config MTD_NAND_BCH
  20. tristate
  21. select BCH
  22. depends on MTD_NAND_ECC_BCH
  23. default MTD_NAND
  24. config MTD_NAND_ECC_BCH
  25. bool "Support software BCH ECC"
  26. default n
  27. help
  28. This enables support for software BCH error correction. Binary BCH
  29. codes are more powerful and cpu intensive than traditional Hamming
  30. ECC codes. They are used with NAND devices requiring more than 1 bit
  31. of error correction.
  32. config MTD_SM_COMMON
  33. tristate
  34. default n
  35. config MTD_NAND_DENALI
  36. tristate
  37. config MTD_NAND_DENALI_PCI
  38. tristate "Support Denali NAND controller on Intel Moorestown"
  39. select MTD_NAND_DENALI
  40. depends on HAS_DMA && PCI
  41. help
  42. Enable the driver for NAND flash on Intel Moorestown, using the
  43. Denali NAND controller core.
  44. config MTD_NAND_DENALI_DT
  45. tristate "Support Denali NAND controller as a DT device"
  46. select MTD_NAND_DENALI
  47. depends on HAS_DMA && HAVE_CLK && OF
  48. help
  49. Enable the driver for NAND flash on platforms using a Denali NAND
  50. controller as a DT device.
  51. config MTD_NAND_GPIO
  52. tristate "GPIO assisted NAND Flash driver"
  53. depends on GPIOLIB || COMPILE_TEST
  54. depends on HAS_IOMEM
  55. help
  56. This enables a NAND flash driver where control signals are
  57. connected to GPIO pins, and commands and data are communicated
  58. via a memory mapped interface.
  59. config MTD_NAND_AMS_DELTA
  60. tristate "NAND Flash device on Amstrad E3"
  61. depends on MACH_AMS_DELTA
  62. default y
  63. help
  64. Support for NAND flash on Amstrad E3 (Delta).
  65. config MTD_NAND_OMAP2
  66. tristate "NAND Flash device on OMAP2, OMAP3, OMAP4 and Keystone"
  67. depends on (ARCH_OMAP2PLUS || ARCH_KEYSTONE)
  68. help
  69. Support for NAND flash on Texas Instruments OMAP2, OMAP3, OMAP4
  70. and Keystone platforms.
  71. config MTD_NAND_OMAP_BCH
  72. depends on MTD_NAND_OMAP2
  73. bool "Support hardware based BCH error correction"
  74. default n
  75. select BCH
  76. help
  77. This config enables the ELM hardware engine, which can be used to
  78. locate and correct errors when using BCH ECC scheme. This offloads
  79. the cpu from doing ECC error searching and correction. However some
  80. legacy OMAP families like OMAP2xxx, OMAP3xxx do not have ELM engine
  81. so this is optional for them.
  82. config MTD_NAND_OMAP_BCH_BUILD
  83. def_tristate MTD_NAND_OMAP2 && MTD_NAND_OMAP_BCH
  84. config MTD_NAND_RICOH
  85. tristate "Ricoh xD card reader"
  86. default n
  87. depends on PCI
  88. select MTD_SM_COMMON
  89. help
  90. Enable support for Ricoh R5C852 xD card reader
  91. You also need to enable ether
  92. NAND SSFDC (SmartMedia) read only translation layer' or new
  93. expermental, readwrite
  94. 'SmartMedia/xD new translation layer'
  95. config MTD_NAND_AU1550
  96. tristate "Au1550/1200 NAND support"
  97. depends on MIPS_ALCHEMY
  98. help
  99. This enables the driver for the NAND flash controller on the
  100. AMD/Alchemy 1550 SOC.
  101. config MTD_NAND_BF5XX
  102. tristate "Blackfin on-chip NAND Flash Controller driver"
  103. depends on BF54x || BF52x
  104. help
  105. This enables the Blackfin on-chip NAND flash controller
  106. No board specific support is done by this driver, each board
  107. must advertise a platform_device for the driver to attach.
  108. This driver can also be built as a module. If so, the module
  109. will be called bf5xx-nand.
  110. config MTD_NAND_BF5XX_HWECC
  111. bool "BF5XX NAND Hardware ECC"
  112. default y
  113. depends on MTD_NAND_BF5XX
  114. help
  115. Enable the use of the BF5XX's internal ECC generator when
  116. using NAND.
  117. config MTD_NAND_BF5XX_BOOTROM_ECC
  118. bool "Use Blackfin BootROM ECC Layout"
  119. default n
  120. depends on MTD_NAND_BF5XX_HWECC
  121. help
  122. If you wish to modify NAND pages and allow the Blackfin on-chip
  123. BootROM to boot from them, say Y here. This is only necessary
  124. if you are booting U-Boot out of NAND and you wish to update
  125. U-Boot from Linux' userspace. Otherwise, you should say N here.
  126. If unsure, say N.
  127. config MTD_NAND_S3C2410
  128. tristate "NAND Flash support for Samsung S3C SoCs"
  129. depends on ARCH_S3C24XX || ARCH_S3C64XX
  130. help
  131. This enables the NAND flash controller on the S3C24xx and S3C64xx
  132. SoCs
  133. No board specific support is done by this driver, each board
  134. must advertise a platform_device for the driver to attach.
  135. config MTD_NAND_S3C2410_DEBUG
  136. bool "Samsung S3C NAND driver debug"
  137. depends on MTD_NAND_S3C2410
  138. help
  139. Enable debugging of the S3C NAND driver
  140. config MTD_NAND_NDFC
  141. tristate "NDFC NanD Flash Controller"
  142. depends on 4xx
  143. select MTD_NAND_ECC_SMC
  144. help
  145. NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
  146. config MTD_NAND_S3C2410_CLKSTOP
  147. bool "Samsung S3C NAND IDLE clock stop"
  148. depends on MTD_NAND_S3C2410
  149. default n
  150. help
  151. Stop the clock to the NAND controller when there is no chip
  152. selected to save power. This will mean there is a small delay
  153. when the is NAND chip selected or released, but will save
  154. approximately 5mA of power when there is nothing happening.
  155. config MTD_NAND_TANGO
  156. tristate "NAND Flash support for Tango chips"
  157. depends on ARCH_TANGO || COMPILE_TEST
  158. depends on HAS_DMA
  159. help
  160. Enables the NAND Flash controller on Tango chips.
  161. config MTD_NAND_DISKONCHIP
  162. tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation)"
  163. depends on HAS_IOMEM
  164. select REED_SOLOMON
  165. select REED_SOLOMON_DEC16
  166. help
  167. This is a reimplementation of M-Systems DiskOnChip 2000,
  168. Millennium and Millennium Plus as a standard NAND device driver,
  169. as opposed to the earlier self-contained MTD device drivers.
  170. This should enable, among other things, proper JFFS2 operation on
  171. these devices.
  172. config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
  173. bool "Advanced detection options for DiskOnChip"
  174. depends on MTD_NAND_DISKONCHIP
  175. help
  176. This option allows you to specify nonstandard address at which to
  177. probe for a DiskOnChip, or to change the detection options. You
  178. are unlikely to need any of this unless you are using LinuxBIOS.
  179. Say 'N'.
  180. config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
  181. hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
  182. depends on MTD_NAND_DISKONCHIP
  183. default "0"
  184. ---help---
  185. By default, the probe for DiskOnChip devices will look for a
  186. DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
  187. This option allows you to specify a single address at which to probe
  188. for the device, which is useful if you have other devices in that
  189. range which get upset when they are probed.
  190. (Note that on PowerPC, the normal probe will only check at
  191. 0xE4000000.)
  192. Normally, you should leave this set to zero, to allow the probe at
  193. the normal addresses.
  194. config MTD_NAND_DISKONCHIP_PROBE_HIGH
  195. bool "Probe high addresses"
  196. depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
  197. help
  198. By default, the probe for DiskOnChip devices will look for a
  199. DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
  200. This option changes to make it probe between 0xFFFC8000 and
  201. 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
  202. useful to you. Say 'N'.
  203. config MTD_NAND_DISKONCHIP_BBTWRITE
  204. bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
  205. depends on MTD_NAND_DISKONCHIP
  206. help
  207. On DiskOnChip devices shipped with the INFTL filesystem (Millennium
  208. and 2000 TSOP/Alon), Linux reserves some space at the end of the
  209. device for the Bad Block Table (BBT). If you have existing INFTL
  210. data on your device (created by non-Linux tools such as M-Systems'
  211. DOS drivers), your data might overlap the area Linux wants to use for
  212. the BBT. If this is a concern for you, leave this option disabled and
  213. Linux will not write BBT data into this area.
  214. The downside of leaving this option disabled is that if bad blocks
  215. are detected by Linux, they will not be recorded in the BBT, which
  216. could cause future problems.
  217. Once you enable this option, new filesystems (INFTL or others, created
  218. in Linux or other operating systems) will not use the reserved area.
  219. The only reason not to enable this option is to prevent damage to
  220. preexisting filesystems.
  221. Even if you leave this disabled, you can enable BBT writes at module
  222. load time (assuming you build diskonchip as a module) with the module
  223. parameter "inftl_bbt_write=1".
  224. config MTD_NAND_DOCG4
  225. tristate "Support for DiskOnChip G4"
  226. depends on HAS_IOMEM
  227. select BCH
  228. select BITREVERSE
  229. help
  230. Support for diskonchip G4 nand flash, found in various smartphones and
  231. PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
  232. Portege G900, Asus P526, and O2 XDA Zinc.
  233. With this driver you will be able to use UBI and create a ubifs on the
  234. device, so you may wish to consider enabling UBI and UBIFS as well.
  235. These devices ship with the Mys/Sandisk SAFTL formatting, for which
  236. there is currently no mtd parser, so you may want to use command line
  237. partitioning to segregate write-protected blocks. On the Treo680, the
  238. first five erase blocks (256KiB each) are write-protected, followed
  239. by the block containing the saftl partition table. This is probably
  240. typical.
  241. config MTD_NAND_SHARPSL
  242. tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
  243. depends on ARCH_PXA
  244. config MTD_NAND_CAFE
  245. tristate "NAND support for OLPC CAFÉ chip"
  246. depends on PCI
  247. select REED_SOLOMON
  248. select REED_SOLOMON_DEC16
  249. help
  250. Use NAND flash attached to the CAFÉ chip designed for the OLPC
  251. laptop.
  252. config MTD_NAND_CS553X
  253. tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
  254. depends on X86_32
  255. depends on !UML && HAS_IOMEM
  256. help
  257. The CS553x companion chips for the AMD Geode processor
  258. include NAND flash controllers with built-in hardware ECC
  259. capabilities; enabling this option will allow you to use
  260. these. The driver will check the MSRs to verify that the
  261. controller is enabled for NAND, and currently requires that
  262. the controller be in MMIO mode.
  263. If you say "m", the module will be called cs553x_nand.
  264. config MTD_NAND_ATMEL
  265. tristate "Support for NAND Flash / SmartMedia on AT91"
  266. depends on ARCH_AT91
  267. help
  268. Enables support for NAND Flash / Smart Media Card interface
  269. on Atmel AT91 processors.
  270. config MTD_NAND_PXA3xx
  271. tristate "NAND support on PXA3xx and Armada 370/XP"
  272. depends on PXA3xx || ARCH_MMP || PLAT_ORION
  273. help
  274. This enables the driver for the NAND flash device found on
  275. PXA3xx processors (NFCv1) and also on Armada 370/XP (NFCv2).
  276. config MTD_NAND_SLC_LPC32XX
  277. tristate "NXP LPC32xx SLC Controller"
  278. depends on ARCH_LPC32XX
  279. help
  280. Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
  281. chips) NAND controller. This is the default for the PHYTEC 3250
  282. reference board which contains a NAND256R3A2CZA6 chip.
  283. Please check the actual NAND chip connected and its support
  284. by the SLC NAND controller.
  285. config MTD_NAND_MLC_LPC32XX
  286. tristate "NXP LPC32xx MLC Controller"
  287. depends on ARCH_LPC32XX
  288. help
  289. Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
  290. controller. This is the default for the WORK92105 controller
  291. board.
  292. Please check the actual NAND chip connected and its support
  293. by the MLC NAND controller.
  294. config MTD_NAND_CM_X270
  295. tristate "Support for NAND Flash on CM-X270 modules"
  296. depends on MACH_ARMCORE
  297. config MTD_NAND_PASEMI
  298. tristate "NAND support for PA Semi PWRficient"
  299. depends on PPC_PASEMI
  300. help
  301. Enables support for NAND Flash interface on PA Semi PWRficient
  302. based boards
  303. config MTD_NAND_TMIO
  304. tristate "NAND Flash device on Toshiba Mobile IO Controller"
  305. depends on MFD_TMIO
  306. help
  307. Support for NAND flash connected to a Toshiba Mobile IO
  308. Controller in some PDAs, including the Sharp SL6000x.
  309. config MTD_NAND_NANDSIM
  310. tristate "Support for NAND Flash Simulator"
  311. help
  312. The simulator may simulate various NAND flash chips for the
  313. MTD nand layer.
  314. config MTD_NAND_GPMI_NAND
  315. tristate "GPMI NAND Flash Controller driver"
  316. depends on MTD_NAND && MXS_DMA
  317. help
  318. Enables NAND Flash support for IMX23, IMX28 or IMX6.
  319. The GPMI controller is very powerful, with the help of BCH
  320. module, it can do the hardware ECC. The GPMI supports several
  321. NAND flashs at the same time. The GPMI may conflicts with other
  322. block, such as SD card. So pay attention to it when you enable
  323. the GPMI.
  324. config MTD_NAND_BRCMNAND
  325. tristate "Broadcom STB NAND controller"
  326. depends on ARM || ARM64 || MIPS
  327. help
  328. Enables the Broadcom NAND controller driver. The controller was
  329. originally designed for Set-Top Box but is used on various BCM7xxx,
  330. BCM3xxx, BCM63xxx, iProc/Cygnus and more.
  331. config MTD_NAND_BCM47XXNFLASH
  332. tristate "Support for NAND flash on BCM4706 BCMA bus"
  333. depends on BCMA_NFLASH
  334. help
  335. BCMA bus can have various flash memories attached, they are
  336. registered by bcma as platform devices. This enables driver for
  337. NAND flash memories. For now only BCM4706 is supported.
  338. config MTD_NAND_PLATFORM
  339. tristate "Support for generic platform NAND driver"
  340. depends on HAS_IOMEM
  341. help
  342. This implements a generic NAND driver for on-SOC platform
  343. devices. You will need to provide platform-specific functions
  344. via platform_data.
  345. config MTD_NAND_ORION
  346. tristate "NAND Flash support for Marvell Orion SoC"
  347. depends on PLAT_ORION
  348. help
  349. This enables the NAND flash controller on Orion machines.
  350. No board specific support is done by this driver, each board
  351. must advertise a platform_device for the driver to attach.
  352. config MTD_NAND_OXNAS
  353. tristate "NAND Flash support for Oxford Semiconductor SoC"
  354. depends on ARCH_OXNAS || COMPILE_TEST
  355. depends on HAS_IOMEM
  356. help
  357. This enables the NAND flash controller on Oxford Semiconductor SoCs.
  358. config MTD_NAND_FSL_ELBC
  359. tristate "NAND support for Freescale eLBC controllers"
  360. depends on FSL_SOC
  361. select FSL_LBC
  362. help
  363. Various Freescale chips, including the 8313, include a NAND Flash
  364. Controller Module with built-in hardware ECC capabilities.
  365. Enabling this option will enable you to use this to control
  366. external NAND devices.
  367. config MTD_NAND_FSL_IFC
  368. tristate "NAND support for Freescale IFC controller"
  369. depends on FSL_SOC || ARCH_LAYERSCAPE || SOC_LS1021A
  370. select FSL_IFC
  371. select MEMORY
  372. help
  373. Various Freescale chips e.g P1010, include a NAND Flash machine
  374. with built-in hardware ECC capabilities.
  375. Enabling this option will enable you to use this to control
  376. external NAND devices.
  377. config MTD_NAND_FSL_UPM
  378. tristate "Support for NAND on Freescale UPM"
  379. depends on PPC_83xx || PPC_85xx
  380. select FSL_LBC
  381. help
  382. Enables support for NAND Flash chips wired onto Freescale PowerPC
  383. processor localbus with User-Programmable Machine support.
  384. config MTD_NAND_MPC5121_NFC
  385. tristate "MPC5121 built-in NAND Flash Controller support"
  386. depends on PPC_MPC512x
  387. help
  388. This enables the driver for the NAND flash controller on the
  389. MPC5121 SoC.
  390. config MTD_NAND_VF610_NFC
  391. tristate "Support for Freescale NFC for VF610/MPC5125"
  392. depends on (SOC_VF610 || COMPILE_TEST)
  393. depends on HAS_IOMEM
  394. help
  395. Enables support for NAND Flash Controller on some Freescale
  396. processors like the VF610, MPC5125, MCF54418 or Kinetis K70.
  397. The driver supports a maximum 2k page size. With 2k pages and
  398. 64 bytes or more of OOB, hardware ECC with up to 32-bit error
  399. correction is supported. Hardware ECC is only enabled through
  400. device tree.
  401. config MTD_NAND_MXC
  402. tristate "MXC NAND support"
  403. depends on ARCH_MXC
  404. help
  405. This enables the driver for the NAND flash controller on the
  406. MXC processors.
  407. config MTD_NAND_SH_FLCTL
  408. tristate "Support for NAND on Renesas SuperH FLCTL"
  409. depends on SUPERH || COMPILE_TEST
  410. depends on HAS_IOMEM
  411. depends on HAS_DMA
  412. help
  413. Several Renesas SuperH CPU has FLCTL. This option enables support
  414. for NAND Flash using FLCTL.
  415. config MTD_NAND_DAVINCI
  416. tristate "Support NAND on DaVinci/Keystone SoC"
  417. depends on ARCH_DAVINCI || (ARCH_KEYSTONE && TI_AEMIF)
  418. help
  419. Enable the driver for NAND flash chips on Texas Instruments
  420. DaVinci/Keystone processors.
  421. config MTD_NAND_TXX9NDFMC
  422. tristate "NAND Flash support for TXx9 SoC"
  423. depends on SOC_TX4938 || SOC_TX4939
  424. help
  425. This enables the NAND flash controller on the TXx9 SoCs.
  426. config MTD_NAND_SOCRATES
  427. tristate "Support for NAND on Socrates board"
  428. depends on SOCRATES
  429. help
  430. Enables support for NAND Flash chips wired onto Socrates board.
  431. config MTD_NAND_NUC900
  432. tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
  433. depends on ARCH_W90X900
  434. help
  435. This enables the driver for the NAND Flash on evaluation board based
  436. on w90p910 / NUC9xx.
  437. config MTD_NAND_JZ4740
  438. tristate "Support for JZ4740 SoC NAND controller"
  439. depends on MACH_JZ4740
  440. help
  441. Enables support for NAND Flash on JZ4740 SoC based boards.
  442. config MTD_NAND_JZ4780
  443. tristate "Support for NAND on JZ4780 SoC"
  444. depends on MACH_JZ4780 && JZ4780_NEMC
  445. help
  446. Enables support for NAND Flash connected to the NEMC on JZ4780 SoC
  447. based boards, using the BCH controller for hardware error correction.
  448. config MTD_NAND_FSMC
  449. tristate "Support for NAND on ST Micros FSMC"
  450. depends on OF
  451. depends on PLAT_SPEAR || ARCH_NOMADIK || ARCH_U8500 || MACH_U300
  452. help
  453. Enables support for NAND Flash chips on the ST Microelectronics
  454. Flexible Static Memory Controller (FSMC)
  455. config MTD_NAND_XWAY
  456. bool "Support for NAND on Lantiq XWAY SoC"
  457. depends on LANTIQ && SOC_TYPE_XWAY
  458. help
  459. Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
  460. to the External Bus Unit (EBU).
  461. config MTD_NAND_SUNXI
  462. tristate "Support for NAND on Allwinner SoCs"
  463. depends on ARCH_SUNXI
  464. help
  465. Enables support for NAND Flash chips on Allwinner SoCs.
  466. config MTD_NAND_HISI504
  467. tristate "Support for NAND controller on Hisilicon SoC Hip04"
  468. depends on HAS_DMA
  469. help
  470. Enables support for NAND controller on Hisilicon SoC Hip04.
  471. config MTD_NAND_QCOM
  472. tristate "Support for NAND on QCOM SoCs"
  473. depends on ARCH_QCOM
  474. help
  475. Enables support for NAND flash chips on SoCs containing the EBI2 NAND
  476. controller. This controller is found on IPQ806x SoC.
  477. config MTD_NAND_MTK
  478. tristate "Support for NAND controller on MTK SoCs"
  479. depends on HAS_DMA
  480. help
  481. Enables support for NAND controller on MTK SoCs.
  482. This controller is found on mt27xx, mt81xx, mt65xx SoCs.
  483. endif # MTD_NAND