Kconfig 7.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225
  1. menuconfig MTD
  2. tristate "Memory Technology Device (MTD) support"
  3. imply NVMEM
  4. help
  5. Memory Technology Devices are flash, RAM and similar chips, often
  6. used for solid state file systems on embedded devices. This option
  7. will provide the generic support for MTD drivers to register
  8. themselves with the kernel and for potential users of MTD devices
  9. to enumerate the devices which are present and obtain a handle on
  10. them. It will also allow you to select individual drivers for
  11. particular hardware and users of MTD devices. If unsure, say N.
  12. if MTD
  13. config MTD_TESTS
  14. tristate "MTD tests support (DANGEROUS)"
  15. depends on m
  16. help
  17. This option includes various MTD tests into compilation. The tests
  18. should normally be compiled as kernel modules. The modules perform
  19. various checks and verifications when loaded.
  20. WARNING: some of the tests will ERASE entire MTD device which they
  21. test. Do not use these tests unless you really know what you do.
  22. menu "Partition parsers"
  23. source "drivers/mtd/parsers/Kconfig"
  24. endmenu
  25. comment "User Modules And Translation Layers"
  26. #
  27. # MTD block device support is select'ed if needed
  28. #
  29. config MTD_BLKDEVS
  30. tristate
  31. config MTD_BLOCK
  32. tristate "Caching block device access to MTD devices"
  33. depends on BLOCK
  34. select MTD_BLKDEVS
  35. help
  36. Although most flash chips have an erase size too large to be useful
  37. as block devices, it is possible to use MTD devices which are based
  38. on RAM chips in this manner. This block device is a user of MTD
  39. devices performing that function.
  40. Note that mounting a JFFS2 filesystem doesn't require using mtdblock.
  41. It's possible to mount a rootfs using the MTD device on the "root="
  42. bootargs as "root=mtd2" or "root=mtd:name_of_device".
  43. Later, it may be extended to perform read/erase/modify/write cycles
  44. on flash chips to emulate a smaller block size. Needless to say,
  45. this is very unsafe, but could be useful for file systems which are
  46. almost never written to.
  47. You do not need this option for use with the DiskOnChip devices. For
  48. those, enable NFTL support (CONFIG_NFTL) instead.
  49. config MTD_BLOCK_RO
  50. tristate "Readonly block device access to MTD devices"
  51. depends on MTD_BLOCK!=y && BLOCK
  52. select MTD_BLKDEVS
  53. help
  54. This allows you to mount read-only file systems (such as cramfs)
  55. from an MTD device, without the overhead (and danger) of the caching
  56. driver.
  57. You do not need this option for use with the DiskOnChip devices. For
  58. those, enable NFTL support (CONFIG_NFTL) instead.
  59. comment "Note that in some cases UBI block is preferred. See MTD_UBI_BLOCK."
  60. depends on MTD_BLOCK || MTD_BLOCK_RO
  61. config FTL
  62. tristate "FTL (Flash Translation Layer) support"
  63. depends on BLOCK
  64. select MTD_BLKDEVS
  65. help
  66. This provides support for the original Flash Translation Layer which
  67. is part of the PCMCIA specification. It uses a kind of pseudo-
  68. file system on a flash device to emulate a block device with
  69. 512-byte sectors, on top of which you put a 'normal' file system.
  70. You may find that the algorithms used in this code are patented
  71. unless you live in the Free World where software patents aren't
  72. legal - in the USA you are only permitted to use this on PCMCIA
  73. hardware, although under the terms of the GPL you're obviously
  74. permitted to copy, modify and distribute the code as you wish. Just
  75. not use it.
  76. config NFTL
  77. tristate "NFTL (NAND Flash Translation Layer) support"
  78. depends on BLOCK
  79. select MTD_BLKDEVS
  80. help
  81. This provides support for the NAND Flash Translation Layer which is
  82. used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
  83. file system on a flash device to emulate a block device with
  84. 512-byte sectors, on top of which you put a 'normal' file system.
  85. You may find that the algorithms used in this code are patented
  86. unless you live in the Free World where software patents aren't
  87. legal - in the USA you are only permitted to use this on DiskOnChip
  88. hardware, although under the terms of the GPL you're obviously
  89. permitted to copy, modify and distribute the code as you wish. Just
  90. not use it.
  91. config NFTL_RW
  92. bool "Write support for NFTL"
  93. depends on NFTL
  94. help
  95. Support for writing to the NAND Flash Translation Layer, as used
  96. on the DiskOnChip.
  97. config INFTL
  98. tristate "INFTL (Inverse NAND Flash Translation Layer) support"
  99. depends on BLOCK
  100. select MTD_BLKDEVS
  101. help
  102. This provides support for the Inverse NAND Flash Translation
  103. Layer which is used on M-Systems' newer DiskOnChip devices. It
  104. uses a kind of pseudo-file system on a flash device to emulate
  105. a block device with 512-byte sectors, on top of which you put
  106. a 'normal' file system.
  107. You may find that the algorithms used in this code are patented
  108. unless you live in the Free World where software patents aren't
  109. legal - in the USA you are only permitted to use this on DiskOnChip
  110. hardware, although under the terms of the GPL you're obviously
  111. permitted to copy, modify and distribute the code as you wish. Just
  112. not use it.
  113. config RFD_FTL
  114. tristate "Resident Flash Disk (Flash Translation Layer) support"
  115. depends on BLOCK
  116. select MTD_BLKDEVS
  117. help
  118. This provides support for the flash translation layer known
  119. as the Resident Flash Disk (RFD), as used by the Embedded BIOS
  120. of General Software. There is a blurb at:
  121. http://www.gensw.com/pages/prod/bios/rfd.htm
  122. config SSFDC
  123. tristate "NAND SSFDC (SmartMedia) read only translation layer"
  124. depends on BLOCK
  125. select MTD_BLKDEVS
  126. help
  127. This enables read only access to SmartMedia formatted NAND
  128. flash. You can mount it with FAT file system.
  129. config SM_FTL
  130. tristate "SmartMedia/xD new translation layer"
  131. depends on BLOCK
  132. select MTD_BLKDEVS
  133. select MTD_NAND_CORE
  134. select MTD_NAND_ECC_SW_HAMMING
  135. help
  136. This enables EXPERIMENTAL R/W support for SmartMedia/xD
  137. FTL (Flash translation layer).
  138. Write support is only lightly tested, therefore this driver
  139. isn't recommended to use with valuable data (anyway if you have
  140. valuable data, do backups regardless of software/hardware you
  141. use, because you never know what will eat your data...)
  142. If you only need R/O access, you can use older R/O driver
  143. (CONFIG_SSFDC)
  144. config MTD_OOPS
  145. tristate "Log panic/oops to an MTD buffer"
  146. help
  147. This enables panic and oops messages to be logged to a circular
  148. buffer in a flash partition where it can be read back at some
  149. later point.
  150. config MTD_PSTORE
  151. tristate "Log panic/oops to an MTD buffer based on pstore"
  152. depends on PSTORE_BLK
  153. help
  154. This enables panic and oops messages to be logged to a circular
  155. buffer in a flash partition where it can be read back as files after
  156. mounting pstore filesystem.
  157. If unsure, say N.
  158. config MTD_SWAP
  159. tristate "Swap on MTD device support"
  160. depends on MTD && SWAP
  161. select MTD_BLKDEVS
  162. help
  163. Provides volatile block device driver on top of mtd partition
  164. suitable for swapping. The mapping of written blocks is not saved.
  165. The driver provides wear leveling by storing erase counter into the
  166. OOB.
  167. config MTD_PARTITIONED_MASTER
  168. bool "Retain master device when partitioned"
  169. default n
  170. depends on MTD
  171. help
  172. For historical reasons, by default, either a master is present or
  173. several partitions are present, but not both. The concern was that
  174. data listed in multiple partitions was dangerous; however, SCSI does
  175. this and it is frequently useful for applications. This config option
  176. leaves the master in even if the device is partitioned. It also makes
  177. the parent of the partition device be the master device, rather than
  178. what lies behind the master.
  179. source "drivers/mtd/chips/Kconfig"
  180. source "drivers/mtd/maps/Kconfig"
  181. source "drivers/mtd/devices/Kconfig"
  182. source "drivers/mtd/nand/Kconfig"
  183. source "drivers/mtd/lpddr/Kconfig"
  184. source "drivers/mtd/spi-nor/Kconfig"
  185. source "drivers/mtd/ubi/Kconfig"
  186. source "drivers/mtd/hyperbus/Kconfig"
  187. endif # MTD