Kconfig 8.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242
  1. # drivers/mtd/nand/Kconfig
  2. # $Id: Kconfig,v 1.35 2005/11/07 11:14:30 gleixner Exp $
  3. menu "NAND Flash Device Drivers"
  4. depends on MTD!=n
  5. config MTD_NAND
  6. tristate "NAND Device Support"
  7. depends on MTD
  8. select MTD_NAND_IDS
  9. help
  10. This enables support for accessing all type of NAND flash
  11. devices. For further information see
  12. <http://www.linux-mtd.infradead.org/doc/nand.html>.
  13. config MTD_NAND_VERIFY_WRITE
  14. bool "Verify NAND page writes"
  15. depends on MTD_NAND
  16. help
  17. This adds an extra check when data is written to the flash. The
  18. NAND flash device internally checks only bits transitioning
  19. from 1 to 0. There is a rare possibility that even though the
  20. device thinks the write was successful, a bit could have been
  21. flipped accidentaly due to device wear or something else.
  22. config MTD_NAND_ECC_SMC
  23. bool "NAND ECC Smart Media byte order"
  24. depends on MTD_NAND
  25. default n
  26. help
  27. Software ECC according to the Smart Media Specification.
  28. The original Linux implementation had byte 0 and 1 swapped.
  29. config MTD_NAND_AUTCPU12
  30. tristate "SmartMediaCard on autronix autcpu12 board"
  31. depends on MTD_NAND && ARCH_AUTCPU12
  32. help
  33. This enables the driver for the autronix autcpu12 board to
  34. access the SmartMediaCard.
  35. config MTD_NAND_EDB7312
  36. tristate "Support for Cirrus Logic EBD7312 evaluation board"
  37. depends on MTD_NAND && ARCH_EDB7312
  38. help
  39. This enables the driver for the Cirrus Logic EBD7312 evaluation
  40. board to access the onboard NAND Flash.
  41. config MTD_NAND_H1900
  42. tristate "iPAQ H1900 flash"
  43. depends on MTD_NAND && ARCH_PXA && MTD_PARTITIONS
  44. help
  45. This enables the driver for the iPAQ h1900 flash.
  46. config MTD_NAND_SPIA
  47. tristate "NAND Flash device on SPIA board"
  48. depends on ARCH_P720T && MTD_NAND
  49. help
  50. If you had to ask, you don't have one. Say 'N'.
  51. config MTD_NAND_AMS_DELTA
  52. tristate "NAND Flash device on Amstrad E3"
  53. depends on MACH_AMS_DELTA && MTD_NAND
  54. help
  55. Support for NAND flash on Amstrad E3 (Delta).
  56. config MTD_NAND_TOTO
  57. tristate "NAND Flash device on TOTO board"
  58. depends on ARCH_OMAP && MTD_NAND && BROKEN
  59. help
  60. Support for NAND flash on Texas Instruments Toto platform.
  61. config MTD_NAND_TS7250
  62. tristate "NAND Flash device on TS-7250 board"
  63. depends on MACH_TS72XX && MTD_NAND
  64. help
  65. Support for NAND flash on Technologic Systems TS-7250 platform.
  66. config MTD_NAND_IDS
  67. tristate
  68. config MTD_NAND_AU1550
  69. tristate "Au1550/1200 NAND support"
  70. depends on (SOC_AU1200 || SOC_AU1550) && MTD_NAND
  71. help
  72. This enables the driver for the NAND flash controller on the
  73. AMD/Alchemy 1550 SOC.
  74. config MTD_NAND_RTC_FROM4
  75. tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
  76. depends on MTD_NAND && SH_SOLUTION_ENGINE
  77. select REED_SOLOMON
  78. select REED_SOLOMON_DEC8
  79. help
  80. This enables the driver for the Renesas Technology AG-AND
  81. flash interface board (FROM_BOARD4)
  82. config MTD_NAND_PPCHAMELEONEVB
  83. tristate "NAND Flash device on PPChameleonEVB board"
  84. depends on PPCHAMELEONEVB && MTD_NAND && BROKEN
  85. help
  86. This enables the NAND flash driver on the PPChameleon EVB Board.
  87. config MTD_NAND_S3C2410
  88. tristate "NAND Flash support for S3C2410/S3C2440 SoC"
  89. depends on ARCH_S3C2410 && MTD_NAND
  90. help
  91. This enables the NAND flash controller on the S3C2410 and S3C2440
  92. SoCs
  93. No board specific support is done by this driver, each board
  94. must advertise a platform_device for the driver to attach.
  95. config MTD_NAND_S3C2410_DEBUG
  96. bool "S3C2410 NAND driver debug"
  97. depends on MTD_NAND_S3C2410
  98. help
  99. Enable debugging of the S3C2410 NAND driver
  100. config MTD_NAND_S3C2410_HWECC
  101. bool "S3C2410 NAND Hardware ECC"
  102. depends on MTD_NAND_S3C2410
  103. help
  104. Enable the use of the S3C2410's internal ECC generator when
  105. using NAND. Early versions of the chip have had problems with
  106. incorrect ECC generation, and if using these, the default of
  107. software ECC is preferable.
  108. If you lay down a device with the hardware ECC, then you will
  109. currently not be able to switch to software, as there is no
  110. implementation for ECC method used by the S3C2410
  111. config MTD_NAND_NDFC
  112. tristate "NDFC NanD Flash Controller"
  113. depends on MTD_NAND && 44x
  114. help
  115. NDFC Nand Flash Controllers are integrated in EP44x SoCs
  116. config MTD_NAND_S3C2410_CLKSTOP
  117. bool "S3C2410 NAND IDLE clock stop"
  118. depends on MTD_NAND_S3C2410
  119. default n
  120. help
  121. Stop the clock to the NAND controller when there is no chip
  122. selected to save power. This will mean there is a small delay
  123. when the is NAND chip selected or released, but will save
  124. approximately 5mA of power when there is nothing happening.
  125. config MTD_NAND_DISKONCHIP
  126. tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
  127. depends on MTD_NAND && EXPERIMENTAL
  128. select REED_SOLOMON
  129. select REED_SOLOMON_DEC16
  130. help
  131. This is a reimplementation of M-Systems DiskOnChip 2000,
  132. Millennium and Millennium Plus as a standard NAND device driver,
  133. as opposed to the earlier self-contained MTD device drivers.
  134. This should enable, among other things, proper JFFS2 operation on
  135. these devices.
  136. config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
  137. bool "Advanced detection options for DiskOnChip"
  138. depends on MTD_NAND_DISKONCHIP
  139. help
  140. This option allows you to specify nonstandard address at which to
  141. probe for a DiskOnChip, or to change the detection options. You
  142. are unlikely to need any of this unless you are using LinuxBIOS.
  143. Say 'N'.
  144. config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
  145. hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
  146. depends on MTD_NAND_DISKONCHIP
  147. default "0"
  148. ---help---
  149. By default, the probe for DiskOnChip devices will look for a
  150. DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
  151. This option allows you to specify a single address at which to probe
  152. for the device, which is useful if you have other devices in that
  153. range which get upset when they are probed.
  154. (Note that on PowerPC, the normal probe will only check at
  155. 0xE4000000.)
  156. Normally, you should leave this set to zero, to allow the probe at
  157. the normal addresses.
  158. config MTD_NAND_DISKONCHIP_PROBE_HIGH
  159. bool "Probe high addresses"
  160. depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
  161. help
  162. By default, the probe for DiskOnChip devices will look for a
  163. DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
  164. This option changes to make it probe between 0xFFFC8000 and
  165. 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
  166. useful to you. Say 'N'.
  167. config MTD_NAND_DISKONCHIP_BBTWRITE
  168. bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
  169. depends on MTD_NAND_DISKONCHIP
  170. help
  171. On DiskOnChip devices shipped with the INFTL filesystem (Millennium
  172. and 2000 TSOP/Alon), Linux reserves some space at the end of the
  173. device for the Bad Block Table (BBT). If you have existing INFTL
  174. data on your device (created by non-Linux tools such as M-Systems'
  175. DOS drivers), your data might overlap the area Linux wants to use for
  176. the BBT. If this is a concern for you, leave this option disabled and
  177. Linux will not write BBT data into this area.
  178. The downside of leaving this option disabled is that if bad blocks
  179. are detected by Linux, they will not be recorded in the BBT, which
  180. could cause future problems.
  181. Once you enable this option, new filesystems (INFTL or others, created
  182. in Linux or other operating systems) will not use the reserved area.
  183. The only reason not to enable this option is to prevent damage to
  184. preexisting filesystems.
  185. Even if you leave this disabled, you can enable BBT writes at module
  186. load time (assuming you build diskonchip as a module) with the module
  187. parameter "inftl_bbt_write=1".
  188. config MTD_NAND_SHARPSL
  189. tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
  190. depends on MTD_NAND && ARCH_PXA
  191. config MTD_NAND_CS553X
  192. tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
  193. depends on MTD_NAND && X86_32 && (X86_PC || X86_GENERICARCH)
  194. help
  195. The CS553x companion chips for the AMD Geode processor
  196. include NAND flash controllers with built-in hardware ECC
  197. capabilities; enabling this option will allow you to use
  198. these. The driver will check the MSRs to verify that the
  199. controller is enabled for NAND, and currently requires that
  200. the controller be in MMIO mode.
  201. If you say "m", the module will be called "cs553x_nand.ko".
  202. config MTD_NAND_NANDSIM
  203. tristate "Support for NAND Flash Simulator"
  204. depends on MTD_NAND && MTD_PARTITIONS
  205. help
  206. The simulator may simulate various NAND flash chips for the
  207. MTD nand layer.
  208. endmenu