Kconfig 17 KB

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