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.ko.
  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_M25P80
  63         tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
  64         depends on SPI_MASTER && EXPERIMENTAL
  65         help
  66           This enables access to most modern SPI flash chips, used for
  67           program and data storage.   Series supported include Atmel AT26DF,
  68           Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X.  Other chips
  69           are supported as well.  See the driver source for the current list,
  70           or to add other chips.
  71
  72           Note that the original DataFlash chips (AT45 series, not AT26DF),
  73           need an entirely different driver.
  74
  75           Set up your spi devices with the right board-specific platform data,
  76           if you want to specify device partitioning or to use a device which
  77           doesn't support the JEDEC ID instruction.
  78
  79 config M25PXX_USE_FAST_READ
  80         bool "Use FAST_READ OPCode allowing SPI CLK <= 50MHz"
  81         depends on MTD_M25P80
  82         default y
  83         help
  84           This option enables FAST_READ access supported by ST M25Pxx.
  85
  86 config MTD_SLRAM
  87         tristate "Uncached system RAM"
  88         help
  89           If your CPU cannot cache all of the physical memory in your machine,
  90           you can still use it for storage or swap by using this driver to
  91           present it to the system as a Memory Technology Device.
  92
  93 config MTD_PHRAM
  94         tristate "Physical system RAM"
  95         help
  96           This is a re-implementation of the slram driver above.
  97
  98           Use this driver to access physical memory that the kernel proper
  99           doesn't have access to, memory beyond the mem=xxx limit, nvram,
 100           memory on the video card, etc...
 101
 102 config MTD_LART
 103         tristate "28F160xx flash driver for LART"
 104         depends on SA1100_LART
 105         help
 106           This enables the flash driver for LART. Please note that you do
 107           not need any mapping/chip driver for LART. This one does it all
 108           for you, so go disable all of those if you enabled some of them (:
 109
 110 config MTD_MTDRAM
 111         tristate "Test driver using RAM"
 112         help
 113           This enables a test MTD device driver which uses vmalloc() to
 114           provide storage.  You probably want to say 'N' unless you're
 115           testing stuff.
 116
 117 config MTDRAM_TOTAL_SIZE
 118         int "MTDRAM device size in KiB"
 119         depends on MTD_MTDRAM
 120         default "4096"
 121         help
 122           This allows you to configure the total size of the MTD device
 123           emulated by the MTDRAM driver.  If the MTDRAM driver is built
 124           as a module, it is also possible to specify this as a parameter when
 125           loading the module.
 126
 127 config MTDRAM_ERASE_SIZE
 128         int "MTDRAM erase block size in KiB"
 129         depends on MTD_MTDRAM
 130         default "128"
 131         help
 132           This allows you to configure the size of the erase blocks in the
 133           device emulated by the MTDRAM driver.  If the MTDRAM driver is built
 134           as a module, it is also possible to specify this as a parameter when
 135           loading the module.
 136
 137 #If not a module (I don't want to test it as a module)
 138 config MTDRAM_ABS_POS
 139         hex "SRAM Hexadecimal Absolute position or 0"
 140         depends on MTD_MTDRAM=y
 141         default "0"
 142         help
 143           If you have system RAM accessible by the CPU but not used by Linux
 144           in normal operation, you can give the physical address at which the
 145           available RAM starts, and the MTDRAM driver will use it instead of
 146           allocating space from Linux's available memory. Otherwise, leave
 147           this set to zero. Most people will want to leave this as zero.
 148
 149 config MTD_BLOCK2MTD
 150         tristate "MTD using block device"
 151         depends on BLOCK
 152         help
 153           This driver allows a block device to appear as an MTD. It would
 154           generally be used in the following cases:
 155
 156           Using Compact Flash as an MTD, these usually present themselves to
 157           the system as an ATA drive.
 158           Testing MTD users (eg JFFS2) on large media and media that might
 159           be removed during a write (using the floppy drive).
 160
 161 comment "Disk-On-Chip Device Drivers"
 162
 163 config MTD_DOC2000
 164         tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
 165         select MTD_DOCPROBE
 166         select MTD_NAND_IDS
 167         ---help---
 168           This provides an MTD device driver for the M-Systems DiskOnChip
 169           2000 and Millennium devices.  Originally designed for the DiskOnChip
 170           2000, it also now includes support for the DiskOnChip Millennium.
 171           If you have problems with this driver and the DiskOnChip Millennium,
 172           you may wish to try the alternative Millennium driver below. To use
 173           the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
 174           in the <file:drivers/mtd/devices/docprobe.c> source code.
 175
 176           If you use this device, you probably also want to enable the NFTL
 177           'NAND Flash Translation Layer' option below, which is used to
 178           emulate a block device by using a kind of file system on the flash
 179           chips.
 180
 181           NOTE: This driver is deprecated and will probably be removed soon.
 182           Please try the new DiskOnChip driver under "NAND Flash Device
 183           Drivers".
 184
 185 config MTD_DOC2001
 186         tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
 187         select MTD_DOCPROBE
 188         select MTD_NAND_IDS
 189         ---help---
 190           This provides an alternative MTD device driver for the M-Systems
 191           DiskOnChip Millennium devices.  Use this if you have problems with
 192           the combined DiskOnChip 2000 and Millennium driver above.  To get
 193           the DiskOnChip probe code to load and use this driver instead of
 194           the other one, you will need to undefine DOC_SINGLE_DRIVER near
 195           the beginning of <file:drivers/mtd/devices/docprobe.c>.
 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_DOC2001PLUS
 207         tristate "M-Systems Disk-On-Chip Millennium Plus"
 208         select MTD_DOCPROBE
 209         select MTD_NAND_IDS
 210         ---help---
 211           This provides an MTD device driver for the M-Systems DiskOnChip
 212           Millennium Plus devices.
 213
 214           If you use this device, you probably also want to enable the INFTL
 215           'Inverse NAND Flash Translation Layer' option below, which is used
 216           to emulate a block device by using a kind of file system on the
 217           flash chips.
 218
 219           NOTE: This driver will soon be replaced by the new DiskOnChip driver
 220           under "NAND Flash Device Drivers" (currently that driver does not
 221           support all Millennium Plus devices).
 222
 223 config MTD_DOCPROBE
 224         tristate
 225         select MTD_DOCECC
 226
 227 config MTD_DOCECC
 228         tristate
 229
 230 config MTD_DOCPROBE_ADVANCED
 231         bool "Advanced detection options for DiskOnChip"
 232         depends on MTD_DOCPROBE
 233         help
 234           This option allows you to specify nonstandard address at which to
 235           probe for a DiskOnChip, or to change the detection options.  You
 236           are unlikely to need any of this unless you are using LinuxBIOS.
 237           Say 'N'.
 238
 239 config MTD_DOCPROBE_ADDRESS
 240         hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
 241         depends on MTD_DOCPROBE
 242         default "0x0000" if MTD_DOCPROBE_ADVANCED
 243         default "0" if !MTD_DOCPROBE_ADVANCED
 244         ---help---
 245           By default, the probe for DiskOnChip devices will look for a
 246           DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
 247           This option allows you to specify a single address at which to probe
 248           for the device, which is useful if you have other devices in that
 249           range which get upset when they are probed.
 250
 251           (Note that on PowerPC, the normal probe will only check at
 252           0xE4000000.)
 253
 254           Normally, you should leave this set to zero, to allow the probe at
 255           the normal addresses.
 256
 257 config MTD_DOCPROBE_HIGH
 258         bool "Probe high addresses"
 259         depends on MTD_DOCPROBE_ADVANCED
 260         help
 261           By default, the probe for DiskOnChip devices will look for a
 262           DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
 263           This option changes to make it probe between 0xFFFC8000 and
 264           0xFFFEE000.  Unless you are using LinuxBIOS, this is unlikely to be
 265           useful to you.  Say 'N'.
 266
 267 config MTD_DOCPROBE_55AA
 268         bool "Probe for 0x55 0xAA BIOS Extension Signature"
 269         depends on MTD_DOCPROBE_ADVANCED
 270         help
 271           Check for the 0x55 0xAA signature of a DiskOnChip, and do not
 272           continue with probing if it is absent.  The signature will always be
 273           present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
 274           Only if you have overwritten the first block of a DiskOnChip
 275           Millennium will it be absent.  Enable this option if you are using
 276           LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
 277           you have managed to wipe the first block.
 278
 279 endmenu
 280