Kconfig 17 KB

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