Kconfig 18 KB

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