drivers/mtd/Kconfig

   1 menuconfig MTD
   2         tristate "Memory Technology Device (MTD) support"
   3         depends on HAS_IOMEM
   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
  13 if MTD
  14
  15 config MTD_DEBUG
  16         bool "Debugging"
  17         help
  18           This turns on low-level debugging for the entire MTD sub-system.
  19           Normally, you should say 'N'.
  20
  21 config MTD_DEBUG_VERBOSE
  22         int "Debugging verbosity (0 = quiet, 3 = noisy)"
  23         depends on MTD_DEBUG
  24         default "0"
  25         help
  26           Determines the verbosity level of the MTD debugging messages.
  27
  28 config MTD_CONCAT
  29         tristate "MTD concatenating support"
  30         help
  31           Support for concatenating several MTD devices into a single
  32           (virtual) one. This allows you to have -for example- a JFFS(2)
  33           file system spanning multiple physical flash chips. If unsure,
  34           say 'Y'.
  35
  36 config MTD_PARTITIONS
  37         bool "MTD partitioning support"
  38         help
  39           If you have a device which needs to divide its flash chip(s) up
  40           into multiple 'partitions', each of which appears to the user as
  41           a separate MTD device, you require this option to be enabled. If
  42           unsure, say 'Y'.
  43
  44           Note, however, that you don't need this option for the DiskOnChip
  45           devices. Partitioning on NFTL 'devices' is a different - that's the
  46           'normal' form of partitioning used on a block device.
  47
  48 config MTD_TESTS
  49         tristate "MTD tests support"
  50         depends on m
  51         help
  52           This option includes various MTD tests into compilation. The tests
  53           should normally be compiled as kernel modules. The modules perform
  54           various checks and verifications when loaded.
  55
  56 config MTD_REDBOOT_PARTS
  57         tristate "RedBoot partition table parsing"
  58         depends on MTD_PARTITIONS
  59         ---help---
  60           RedBoot is a ROM monitor and bootloader which deals with multiple
  61           'images' in flash devices by putting a table one of the erase
  62           blocks on the device, similar to a partition table, which gives
  63           the offsets, lengths and names of all the images stored in the
  64           flash.
  65
  66           If you need code which can detect and parse this table, and register
  67           MTD 'partitions' corresponding to each image in the table, enable
  68           this option.
  69
  70           You will still need the parsing functions to be called by the driver
  71           for your particular device. It won't happen automatically. The
  72           SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
  73           example.
  74
  75 config MTD_REDBOOT_DIRECTORY_BLOCK
  76         int "Location of RedBoot partition table"
  77         depends on MTD_REDBOOT_PARTS
  78         default "-1"
  79         ---help---
  80           This option is the Linux counterpart to the
  81           CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time
  82           option.
  83
  84           The option specifies which Flash sectors holds the RedBoot
  85           partition table.  A zero or positive value gives an absolute
  86           erase block number. A negative value specifies a number of
  87           sectors before the end of the device.
  88
  89           For example "2" means block number 2, "-1" means the last
  90           block and "-2" means the penultimate block.
  91
  92 config MTD_REDBOOT_PARTS_UNALLOCATED
  93         bool "Include unallocated flash regions"
  94         depends on MTD_REDBOOT_PARTS
  95         help
  96           If you need to register each unallocated flash region as a MTD
  97           'partition', enable this option.
  98
  99 config MTD_REDBOOT_PARTS_READONLY
 100         bool "Force read-only for RedBoot system images"
 101         depends on MTD_REDBOOT_PARTS
 102         help
 103           If you need to force read-only for 'RedBoot', 'RedBoot Config' and
 104           'FIS directory' images, enable this option.
 105
 106 config MTD_CMDLINE_PARTS
 107         bool "Command line partition table parsing"
 108         depends on MTD_PARTITIONS = "y" && MTD = "y"
 109         ---help---
 110           Allow generic configuration of the MTD partition tables via the kernel
 111           command line. Multiple flash resources are supported for hardware where
 112           different kinds of flash memory are available.
 113
 114           You will still need the parsing functions to be called by the driver
 115           for your particular device. It won't happen automatically. The
 116           SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
 117           example.
 118
 119           The format for the command line is as follows:
 120
 121           mtdparts=<mtddef>[;<mtddef]
 122           <mtddef>  := <mtd-id>:<partdef>[,<partdef>]
 123           <partdef> := <size>[@offset][<name>][ro]
 124           <mtd-id>  := unique id used in mapping driver/device
 125           <size>    := standard linux memsize OR "-" to denote all
 126           remaining space
 127           <name>    := (NAME)
 128
 129           Due to the way Linux handles the command line, no spaces are
 130           allowed in the partition definition, including mtd id's and partition
 131           names.
 132
 133           Examples:
 134
 135           1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
 136           mtdparts=sa1100:-
 137
 138           Same flash, but 2 named partitions, the first one being read-only:
 139           mtdparts=sa1100:256k(ARMboot)ro,-(root)
 140
 141           If unsure, say 'N'.
 142
 143 config MTD_AFS_PARTS
 144         tristate "ARM Firmware Suite partition parsing"
 145         depends on ARM && MTD_PARTITIONS
 146         ---help---
 147           The ARM Firmware Suite allows the user to divide flash devices into
 148           multiple 'images'. Each such image has a header containing its name
 149           and offset/size etc.
 150
 151           If you need code which can detect and parse these tables, and
 152           register MTD 'partitions' corresponding to each image detected,
 153           enable this option.
 154
 155           You will still need the parsing functions to be called by the driver
 156           for your particular device. It won't happen automatically. The
 157           'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example.
 158
 159 config MTD_OF_PARTS
 160         tristate "Flash partition map based on OF description"
 161         depends on PPC_OF && MTD_PARTITIONS
 162         help
 163           This provides a partition parsing function which derives
 164           the partition map from the children of the flash node,
 165           as described in Documentation/powerpc/booting-without-of.txt.
 166
 167 config MTD_AR7_PARTS
 168         tristate "TI AR7 partitioning support"
 169         depends on MTD_PARTITIONS
 170         ---help---
 171           TI AR7 partitioning support
 172
 173 comment "User Modules And Translation Layers"
 174
 175 config MTD_CHAR
 176         tristate "Direct char device access to MTD devices"
 177         help
 178           This provides a character device for each MTD device present in
 179           the system, allowing the user to read and write directly to the
 180           memory chips, and also use ioctl() to obtain information about
 181           the device, or to erase parts of it.
 182
 183 config HAVE_MTD_OTP
 184         bool
 185         help
 186           Enable access to OTP regions using MTD_CHAR.
 187
 188 config MTD_BLKDEVS
 189         tristate "Common interface to block layer for MTD 'translation layers'"
 190         depends on BLOCK
 191         default n
 192
 193 config MTD_BLOCK
 194         tristate "Caching block device access to MTD devices"
 195         depends on BLOCK
 196         select MTD_BLKDEVS
 197         ---help---
 198           Although most flash chips have an erase size too large to be useful
 199           as block devices, it is possible to use MTD devices which are based
 200           on RAM chips in this manner. This block device is a user of MTD
 201           devices performing that function.
 202
 203           At the moment, it is also required for the Journalling Flash File
 204           System(s) to obtain a handle on the MTD device when it's mounted
 205           (although JFFS and JFFS2 don't actually use any of the functionality
 206           of the mtdblock device).
 207
 208           Later, it may be extended to perform read/erase/modify/write cycles
 209           on flash chips to emulate a smaller block size. Needless to say,
 210           this is very unsafe, but could be useful for file systems which are
 211           almost never written to.
 212
 213           You do not need this option for use with the DiskOnChip devices. For
 214           those, enable NFTL support (CONFIG_NFTL) instead.
 215
 216 config MTD_BLOCK_RO
 217         tristate "Readonly block device access to MTD devices"
 218         depends on MTD_BLOCK!=y && BLOCK
 219         select MTD_BLKDEVS
 220         help
 221           This allows you to mount read-only file systems (such as cramfs)
 222           from an MTD device, without the overhead (and danger) of the caching
 223           driver.
 224
 225           You do not need this option for use with the DiskOnChip devices. For
 226           those, enable NFTL support (CONFIG_NFTL) instead.
 227
 228 config FTL
 229         tristate "FTL (Flash Translation Layer) support"
 230         depends on BLOCK
 231         select MTD_BLKDEVS
 232         ---help---
 233           This provides support for the original Flash Translation Layer which
 234           is part of the PCMCIA specification. It uses a kind of pseudo-
 235           file system on a flash device to emulate a block device with
 236           512-byte sectors, on top of which you put a 'normal' file system.
 237
 238           You may find that the algorithms used in this code are patented
 239           unless you live in the Free World where software patents aren't
 240           legal - in the USA you are only permitted to use this on PCMCIA
 241           hardware, although under the terms of the GPL you're obviously
 242           permitted to copy, modify and distribute the code as you wish. Just
 243           not use it.
 244
 245 config NFTL
 246         tristate "NFTL (NAND Flash Translation Layer) support"
 247         depends on BLOCK
 248         select MTD_BLKDEVS
 249         ---help---
 250           This provides support for the NAND Flash Translation Layer which is
 251           used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
 252           file system on a flash device to emulate a block device with
 253           512-byte sectors, on top of which you put a 'normal' file system.
 254
 255           You may find that the algorithms used in this code are patented
 256           unless you live in the Free World where software patents aren't
 257           legal - in the USA you are only permitted to use this on DiskOnChip
 258           hardware, although under the terms of the GPL you're obviously
 259           permitted to copy, modify and distribute the code as you wish. Just
 260           not use it.
 261
 262 config NFTL_RW
 263         bool "Write support for NFTL"
 264         depends on NFTL
 265         help
 266           Support for writing to the NAND Flash Translation Layer, as used
 267           on the DiskOnChip.
 268
 269 config INFTL
 270         tristate "INFTL (Inverse NAND Flash Translation Layer) support"
 271         depends on BLOCK
 272         select MTD_BLKDEVS
 273         ---help---
 274           This provides support for the Inverse NAND Flash Translation
 275           Layer which is used on M-Systems' newer DiskOnChip devices. It
 276           uses a kind of pseudo-file system on a flash device to emulate
 277           a block device with 512-byte sectors, on top of which you put
 278           a 'normal' file system.
 279
 280           You may find that the algorithms used in this code are patented
 281           unless you live in the Free World where software patents aren't
 282           legal - in the USA you are only permitted to use this on DiskOnChip
 283           hardware, although under the terms of the GPL you're obviously
 284           permitted to copy, modify and distribute the code as you wish. Just
 285           not use it.
 286
 287 config RFD_FTL
 288         tristate "Resident Flash Disk (Flash Translation Layer) support"
 289         depends on BLOCK
 290         select MTD_BLKDEVS
 291         ---help---
 292           This provides support for the flash translation layer known
 293           as the Resident Flash Disk (RFD), as used by the Embedded BIOS
 294           of General Software. There is a blurb at:
 295
 296                 http://www.gensw.com/pages/prod/bios/rfd.htm
 297
 298 config SSFDC
 299         tristate "NAND SSFDC (SmartMedia) read only translation layer"
 300         depends on BLOCK
 301         select MTD_BLKDEVS
 302         help
 303           This enables read only access to SmartMedia formatted NAND
 304           flash. You can mount it with FAT file system.
 305
 306 config MTD_OOPS
 307         tristate "Log panic/oops to an MTD buffer"
 308         depends on MTD
 309         help
 310           This enables panic and oops messages to be logged to a circular
 311           buffer in a flash partition where it can be read back at some
 312           later point.
 313
 314           To use, add console=ttyMTDx to the kernel command line,
 315           where x is the MTD device number to use.
 316
 317 source "drivers/mtd/chips/Kconfig"
 318
 319 source "drivers/mtd/maps/Kconfig"
 320
 321 source "drivers/mtd/devices/Kconfig"
 322
 323 source "drivers/mtd/nand/Kconfig"
 324
 325 source "drivers/mtd/onenand/Kconfig"
 326
 327 source "drivers/mtd/lpddr/Kconfig"
 328
 329 source "drivers/mtd/ubi/Kconfig"
 330
 331 endif # MTD