Kconfig 19 KB

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