drivers/mtd/devices/Kconfig

   1 # drivers/mtd/maps/Kconfig
   2
   3 menu "Self-contained MTD device drivers"
   4         depends on MTD!=n
   5
   6 config MTD_PMC551
   7         tristate "Ramix PMC551 PCI Mezzanine RAM card support"
   8         depends on PCI
   9         ---help---
  10           This provides a MTD device driver for the Ramix PMC551 RAM PCI card
  11           from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
  12           These devices come in memory configurations from 32M - 1G.  If you
  13           have one, you probably want to enable this.
  14
  15           If this driver is compiled as a module you get the ability to select
  16           the size of the aperture window pointing into the devices memory.
  17           What this means is that if you have a 1G card, normally the kernel
  18           will use a 1G memory map as its view of the device.  As a module,
  19           you can select a 1M window into the memory and the driver will
  20           "slide" the window around the PMC551's memory.  This was
  21           particularly useful on the 2.2 kernels on PPC architectures as there
  22           was limited kernel space to deal with.
  23
  24 config MTD_PMC551_BUGFIX
  25         bool "PMC551 256M DRAM Bugfix"
  26         depends on MTD_PMC551
  27         help
  28           Some of Ramix's PMC551 boards with 256M configurations have invalid
  29           column and row mux values.  This option will fix them, but will
  30           break other memory configurations.  If unsure say N.
  31
  32 config MTD_PMC551_DEBUG
  33         bool "PMC551 Debugging"
  34         depends on MTD_PMC551
  35         help
  36           This option makes the PMC551 more verbose during its operation and
  37           is only really useful if you are developing on this driver or
  38           suspect a possible hardware or driver bug.  If unsure say N.
  39
  40 config MTD_MS02NV
  41         tristate "DEC MS02-NV NVRAM module support"
  42         depends on MACH_DECSTATION
  43         help
  44           This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
  45           backed-up NVRAM module.  The module was originally meant as an NFS
  46           accelerator.  Say Y here if you have a DECstation 5000/2x0 or a
  47           DECsystem 5900 equipped with such a module.
  48
  49           If you want to compile this driver as a module ( = code which can be
  50           inserted in and removed from the running kernel whenever you want),
  51           say M here and read <file:Documentation/kbuild/modules.txt>.
  52           The module will be called ms02-nv.
  53
  54 config MTD_DATAFLASH
  55         tristate "Support for AT45xxx DataFlash"
  56         depends on SPI_MASTER && EXPERIMENTAL
  57         help
  58           This enables access to AT45xxx DataFlash chips, using SPI.
  59           Sometimes DataFlash chips are packaged inside MMC-format
  60           cards; at this writing, the MMC stack won't handle those.
  61
  62 config MTD_DATAFLASH_WRITE_VERIFY
  63         bool "Verify DataFlash page writes"
  64         depends on MTD_DATAFLASH
  65         help
  66           This adds an extra check when data is written to the flash.
  67           It may help if you are verifying chip setup (timings etc) on
  68           your board.  There is a rare possibility that even though the
  69           device thinks the write was successful, a bit could have been
  70           flipped accidentally due to device wear or something else.
  71
  72 config MTD_DATAFLASH_OTP
  73         bool "DataFlash OTP support (Security Register)"
  74         depends on MTD_DATAFLASH
  75         select HAVE_MTD_OTP
  76         help
  77           Newer DataFlash chips (revisions C and D) support 128 bytes of
  78           one-time-programmable (OTP) data.  The first half may be written
  79           (once) with up to 64 bytes of data, such as a serial number or
  80           other key product data.  The second half is programmed with a
  81           unique-to-each-chip bit pattern at the factory.
  82
  83 config MTD_M25P80
  84         tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
  85         depends on SPI_MASTER && EXPERIMENTAL
  86         help
  87           This enables access to most modern SPI flash chips, used for
  88           program and data storage.   Series supported include Atmel AT26DF,
  89           Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X.  Other chips
  90           are supported as well.  See the driver source for the current list,
  91           or to add other chips.
  92
  93           Note that the original DataFlash chips (AT45 series, not AT26DF),
  94           need an entirely different driver.
  95
  96           Set up your spi devices with the right board-specific platform data,
  97           if you want to specify device partitioning or to use a device which
  98           doesn't support the JEDEC ID instruction.
  99
 100 config M25PXX_USE_FAST_READ
 101         bool "Use FAST_READ OPCode allowing SPI CLK <= 50MHz"
 102         depends on MTD_M25P80
 103         default y
 104         help
 105           This option enables FAST_READ access supported by ST M25Pxx.
 106
 107 config MTD_SLRAM
 108         tristate "Uncached system RAM"
 109         help
 110           If your CPU cannot cache all of the physical memory in your machine,
 111           you can still use it for storage or swap by using this driver to
 112           present it to the system as a Memory Technology Device.
 113
 114 config MTD_PHRAM
 115         tristate "Physical system RAM"
 116         help
 117           This is a re-implementation of the slram driver above.
 118
 119           Use this driver to access physical memory that the kernel proper
 120           doesn't have access to, memory beyond the mem=xxx limit, nvram,
 121           memory on the video card, etc...
 122
 123 config MTD_LART
 124         tristate "28F160xx flash driver for LART"
 125         depends on SA1100_LART
 126         help
 127           This enables the flash driver for LART. Please note that you do
 128           not need any mapping/chip driver for LART. This one does it all
 129           for you, so go disable all of those if you enabled some of them (:
 130
 131 config MTD_MTDRAM
 132         tristate "Test driver using RAM"
 133         help
 134           This enables a test MTD device driver which uses vmalloc() to
 135           provide storage.  You probably want to say 'N' unless you're
 136           testing stuff.
 137
 138 config MTDRAM_TOTAL_SIZE
 139         int "MTDRAM device size in KiB"
 140         depends on MTD_MTDRAM
 141         default "4096"
 142         help
 143           This allows you to configure the total size of the MTD device
 144           emulated by the MTDRAM driver.  If the MTDRAM driver is built
 145           as a module, it is also possible to specify this as a parameter when
 146           loading the module.
 147
 148 config MTDRAM_ERASE_SIZE
 149         int "MTDRAM erase block size in KiB"
 150         depends on MTD_MTDRAM
 151         default "128"
 152         help
 153           This allows you to configure the size of the erase blocks in the
 154           device emulated by the MTDRAM driver.  If the MTDRAM driver is built
 155           as a module, it is also possible to specify this as a parameter when
 156           loading the module.
 157
 158 #If not a module (I don't want to test it as a module)
 159 config MTDRAM_ABS_POS
 160         hex "SRAM Hexadecimal Absolute position or 0"
 161         depends on MTD_MTDRAM=y
 162         default "0"
 163         help
 164           If you have system RAM accessible by the CPU but not used by Linux
 165           in normal operation, you can give the physical address at which the
 166           available RAM starts, and the MTDRAM driver will use it instead of
 167           allocating space from Linux's available memory. Otherwise, leave
 168           this set to zero. Most people will want to leave this as zero.
 169
 170 config MTD_BLOCK2MTD
 171         tristate "MTD using block device"
 172         depends on BLOCK
 173         help
 174           This driver allows a block device to appear as an MTD. It would
 175           generally be used in the following cases:
 176
 177           Using Compact Flash as an MTD, these usually present themselves to
 178           the system as an ATA drive.
 179           Testing MTD users (eg JFFS2) on large media and media that might
 180           be removed during a write (using the floppy drive).
 181
 182 comment "Disk-On-Chip Device Drivers"
 183
 184 config MTD_DOC2000
 185         tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
 186         select MTD_DOCPROBE
 187         select MTD_NAND_IDS
 188         ---help---
 189           This provides an MTD device driver for the M-Systems DiskOnChip
 190           2000 and Millennium devices.  Originally designed for the DiskOnChip
 191           2000, it also now includes support for the DiskOnChip Millennium.
 192           If you have problems with this driver and the DiskOnChip Millennium,
 193           you may wish to try the alternative Millennium driver below. To use
 194           the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
 195           in the <file:drivers/mtd/devices/docprobe.c> source code.
 196
 197           If you use this device, you probably also want to enable the NFTL
 198           'NAND Flash Translation Layer' option below, which is used to
 199           emulate a block device by using a kind of file system on the flash
 200           chips.
 201
 202           NOTE: This driver is deprecated and will probably be removed soon.
 203           Please try the new DiskOnChip driver under "NAND Flash Device
 204           Drivers".
 205
 206 config MTD_DOC2001
 207         tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
 208         select MTD_DOCPROBE
 209         select MTD_NAND_IDS
 210         ---help---
 211           This provides an alternative MTD device driver for the M-Systems
 212           DiskOnChip Millennium devices.  Use this if you have problems with
 213           the combined DiskOnChip 2000 and Millennium driver above.  To get
 214           the DiskOnChip probe code to load and use this driver instead of
 215           the other one, you will need to undefine DOC_SINGLE_DRIVER near
 216           the beginning of <file:drivers/mtd/devices/docprobe.c>.
 217
 218           If you use this device, you probably also want to enable the NFTL
 219           'NAND Flash Translation Layer' option below, which is used to
 220           emulate a block device by using a kind of file system on the flash
 221           chips.
 222
 223           NOTE: This driver is deprecated and will probably be removed soon.
 224           Please try the new DiskOnChip driver under "NAND Flash Device
 225           Drivers".
 226
 227 config MTD_DOC2001PLUS
 228         tristate "M-Systems Disk-On-Chip Millennium Plus"
 229         select MTD_DOCPROBE
 230         select MTD_NAND_IDS
 231         ---help---
 232           This provides an MTD device driver for the M-Systems DiskOnChip
 233           Millennium Plus devices.
 234
 235           If you use this device, you probably also want to enable the INFTL
 236           'Inverse NAND Flash Translation Layer' option below, which is used
 237           to emulate a block device by using a kind of file system on the
 238           flash chips.
 239
 240           NOTE: This driver will soon be replaced by the new DiskOnChip driver
 241           under "NAND Flash Device Drivers" (currently that driver does not
 242           support all Millennium Plus devices).
 243
 244 config MTD_DOCPROBE
 245         tristate
 246         select MTD_DOCECC
 247
 248 config MTD_DOCECC
 249         tristate
 250
 251 config MTD_DOCPROBE_ADVANCED
 252         bool "Advanced detection options for DiskOnChip"
 253         depends on MTD_DOCPROBE
 254         help
 255           This option allows you to specify nonstandard address at which to
 256           probe for a DiskOnChip, or to change the detection options.  You
 257           are unlikely to need any of this unless you are using LinuxBIOS.
 258           Say 'N'.
 259
 260 config MTD_DOCPROBE_ADDRESS
 261         hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
 262         depends on MTD_DOCPROBE
 263         default "0x0000" if MTD_DOCPROBE_ADVANCED
 264         default "0" if !MTD_DOCPROBE_ADVANCED
 265         ---help---
 266           By default, the probe for DiskOnChip devices will look for a
 267           DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
 268           This option allows you to specify a single address at which to probe
 269           for the device, which is useful if you have other devices in that
 270           range which get upset when they are probed.
 271
 272           (Note that on PowerPC, the normal probe will only check at
 273           0xE4000000.)
 274
 275           Normally, you should leave this set to zero, to allow the probe at
 276           the normal addresses.
 277
 278 config MTD_DOCPROBE_HIGH
 279         bool "Probe high addresses"
 280         depends on MTD_DOCPROBE_ADVANCED
 281         help
 282           By default, the probe for DiskOnChip devices will look for a
 283           DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
 284           This option changes to make it probe between 0xFFFC8000 and
 285           0xFFFEE000.  Unless you are using LinuxBIOS, this is unlikely to be
 286           useful to you.  Say 'N'.
 287
 288 config MTD_DOCPROBE_55AA
 289         bool "Probe for 0x55 0xAA BIOS Extension Signature"
 290         depends on MTD_DOCPROBE_ADVANCED
 291         help
 292           Check for the 0x55 0xAA signature of a DiskOnChip, and do not
 293           continue with probing if it is absent.  The signature will always be
 294           present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
 295           Only if you have overwritten the first block of a DiskOnChip
 296           Millennium will it be absent.  Enable this option if you are using
 297           LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
 298           you have managed to wipe the first block.
 299
 300 endmenu
 301