Kconfig 8.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236
  1. menu "Self-contained MTD device drivers"
  2. depends on MTD!=n
  3. depends on HAS_IOMEM
  4. config MTD_PMC551
  5. tristate "Ramix PMC551 PCI Mezzanine RAM card support"
  6. depends on PCI
  7. help
  8. This provides a MTD device driver for the Ramix PMC551 RAM PCI card
  9. from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
  10. These devices come in memory configurations from 32M - 1G. If you
  11. have one, you probably want to enable this.
  12. If this driver is compiled as a module you get the ability to select
  13. the size of the aperture window pointing into the devices memory.
  14. What this means is that if you have a 1G card, normally the kernel
  15. will use a 1G memory map as its view of the device. As a module,
  16. you can select a 1M window into the memory and the driver will
  17. "slide" the window around the PMC551's memory. This was
  18. particularly useful on the 2.2 kernels on PPC architectures as there
  19. was limited kernel space to deal with.
  20. config MTD_PMC551_BUGFIX
  21. bool "PMC551 256M DRAM Bugfix"
  22. depends on MTD_PMC551
  23. help
  24. Some of Ramix's PMC551 boards with 256M configurations have invalid
  25. column and row mux values. This option will fix them, but will
  26. break other memory configurations. If unsure say N.
  27. config MTD_PMC551_DEBUG
  28. bool "PMC551 Debugging"
  29. depends on MTD_PMC551
  30. help
  31. This option makes the PMC551 more verbose during its operation and
  32. is only really useful if you are developing on this driver or
  33. suspect a possible hardware or driver bug. If unsure say N.
  34. config MTD_MS02NV
  35. tristate "DEC MS02-NV NVRAM module support"
  36. depends on MACH_DECSTATION
  37. help
  38. This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
  39. backed-up NVRAM module. The module was originally meant as an NFS
  40. accelerator. Say Y here if you have a DECstation 5000/2x0 or a
  41. DECsystem 5900 equipped with such a module.
  42. If you want to compile this driver as a module ( = code which can be
  43. inserted in and removed from the running kernel whenever you want),
  44. say M here and read <file:Documentation/kbuild/modules.txt>.
  45. The module will be called ms02-nv.
  46. config MTD_DATAFLASH
  47. tristate "Support for AT45xxx DataFlash"
  48. depends on SPI_MASTER
  49. help
  50. This enables access to AT45xxx DataFlash chips, using SPI.
  51. Sometimes DataFlash chips are packaged inside MMC-format
  52. cards; at this writing, the MMC stack won't handle those.
  53. config MTD_DATAFLASH_WRITE_VERIFY
  54. bool "Verify DataFlash page writes"
  55. depends on MTD_DATAFLASH
  56. help
  57. This adds an extra check when data is written to the flash.
  58. It may help if you are verifying chip setup (timings etc) on
  59. your board. There is a rare possibility that even though the
  60. device thinks the write was successful, a bit could have been
  61. flipped accidentally due to device wear or something else.
  62. config MTD_DATAFLASH_OTP
  63. bool "DataFlash OTP support (Security Register)"
  64. depends on MTD_DATAFLASH
  65. help
  66. Newer DataFlash chips (revisions C and D) support 128 bytes of
  67. one-time-programmable (OTP) data. The first half may be written
  68. (once) with up to 64 bytes of data, such as a serial number or
  69. other key product data. The second half is programmed with a
  70. unique-to-each-chip bit pattern at the factory.
  71. config MTD_M25P80
  72. tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
  73. depends on SPI_MASTER && MTD_SPI_NOR
  74. select SPI_MEM
  75. help
  76. This enables access to most modern SPI flash chips, used for
  77. program and data storage. Series supported include Atmel AT26DF,
  78. Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X. Other chips
  79. are supported as well. See the driver source for the current list,
  80. or to add other chips.
  81. Note that the original DataFlash chips (AT45 series, not AT26DF),
  82. need an entirely different driver.
  83. Set up your spi devices with the right board-specific platform data,
  84. if you want to specify device partitioning or to use a device which
  85. doesn't support the JEDEC ID instruction.
  86. config MTD_MCHP23K256
  87. tristate "Microchip 23K256 SRAM"
  88. depends on SPI_MASTER
  89. help
  90. This enables access to Microchip 23K256 SRAM chips, using SPI.
  91. Set up your spi devices with the right board-specific
  92. platform data, or a device tree description if you want to
  93. specify device partitioning
  94. config MTD_SPEAR_SMI
  95. tristate "SPEAR MTD NOR Support through SMI controller"
  96. depends on PLAT_SPEAR
  97. default y
  98. help
  99. This enable SNOR support on SPEAR platforms using SMI controller
  100. config MTD_SST25L
  101. tristate "Support SST25L (non JEDEC) SPI Flash chips"
  102. depends on SPI_MASTER
  103. help
  104. This enables access to the non JEDEC SST25L SPI flash chips, used
  105. for program and data storage.
  106. Set up your spi devices with the right board-specific platform data,
  107. if you want to specify device partitioning.
  108. config MTD_BCM47XXSFLASH
  109. tristate "Support for serial flash on BCMA bus"
  110. depends on BCMA_SFLASH && (MIPS || ARM)
  111. help
  112. BCMA bus can have various flash memories attached, they are
  113. registered by bcma as platform devices. This enables driver for
  114. serial flash memories.
  115. config MTD_SLRAM
  116. tristate "Uncached system RAM"
  117. help
  118. If your CPU cannot cache all of the physical memory in your machine,
  119. you can still use it for storage or swap by using this driver to
  120. present it to the system as a Memory Technology Device.
  121. config MTD_PHRAM
  122. tristate "Physical system RAM"
  123. help
  124. This is a re-implementation of the slram driver above.
  125. Use this driver to access physical memory that the kernel proper
  126. doesn't have access to, memory beyond the mem=xxx limit, nvram,
  127. memory on the video card, etc...
  128. config MTD_LART
  129. tristate "28F160xx flash driver for LART"
  130. depends on SA1100_LART
  131. help
  132. This enables the flash driver for LART. Please note that you do
  133. not need any mapping/chip driver for LART. This one does it all
  134. for you, so go disable all of those if you enabled some of them (:
  135. config MTD_MTDRAM
  136. tristate "Test driver using RAM"
  137. help
  138. This enables a test MTD device driver which uses vmalloc() to
  139. provide storage. You probably want to say 'N' unless you're
  140. testing stuff.
  141. config MTDRAM_TOTAL_SIZE
  142. int "MTDRAM device size in KiB"
  143. depends on MTD_MTDRAM
  144. default "4096"
  145. help
  146. This allows you to configure the total size of the MTD device
  147. emulated by the MTDRAM driver. If the MTDRAM driver is built
  148. as a module, it is also possible to specify this as a parameter when
  149. loading the module.
  150. config MTDRAM_ERASE_SIZE
  151. int "MTDRAM erase block size in KiB"
  152. depends on MTD_MTDRAM
  153. default "128"
  154. help
  155. This allows you to configure the size of the erase blocks in the
  156. device emulated by the MTDRAM driver. If the MTDRAM driver is built
  157. as a module, it is also possible to specify this as a parameter when
  158. loading the module.
  159. config MTD_BLOCK2MTD
  160. tristate "MTD using block device"
  161. depends on BLOCK
  162. help
  163. This driver allows a block device to appear as an MTD. It would
  164. generally be used in the following cases:
  165. Using Compact Flash as an MTD, these usually present themselves to
  166. the system as an ATA drive.
  167. Testing MTD users (eg JFFS2) on large media and media that might
  168. be removed during a write (using the floppy drive).
  169. config MTD_POWERNV_FLASH
  170. tristate "powernv flash MTD driver"
  171. depends on PPC_POWERNV
  172. help
  173. This provides an MTD device to access flash on powernv OPAL
  174. platforms from Linux. This device abstracts away the
  175. firmware interface for flash access.
  176. comment "Disk-On-Chip Device Drivers"
  177. config MTD_DOCG3
  178. tristate "M-Systems Disk-On-Chip G3"
  179. select BCH
  180. select BCH_CONST_PARAMS if !MTD_NAND_BCH
  181. select BITREVERSE
  182. help
  183. This provides an MTD device driver for the M-Systems DiskOnChip
  184. G3 devices.
  185. The driver provides access to G3 DiskOnChip, distributed by
  186. M-Systems and now Sandisk. The support is very experimental,
  187. and doesn't give access to any write operations.
  188. config MTD_ST_SPI_FSM
  189. tristate "ST Microelectronics SPI FSM Serial Flash Controller"
  190. depends on ARCH_STI
  191. help
  192. This provides an MTD device driver for the ST Microelectronics
  193. SPI Fast Sequence Mode (FSM) Serial Flash Controller and support
  194. for a subset of connected Serial Flash devices.
  195. if MTD_DOCG3
  196. config BCH_CONST_M
  197. default 14
  198. config BCH_CONST_T
  199. default 4
  200. endif
  201. endmenu