xref: /openbmc/linux/drivers/mtd/devices/Kconfig (revision 1d6432fe10c3e724e307dd7137cd293a0edcae80)
11da177e4SLinus Torvalds# drivers/mtd/maps/Kconfig
2e5580fbeSThomas Gleixner# $Id: Kconfig,v 1.18 2005/11/07 11:14:24 gleixner Exp $
31da177e4SLinus Torvalds
41da177e4SLinus Torvaldsmenu "Self-contained MTD device drivers"
51da177e4SLinus Torvalds	depends on MTD!=n
61da177e4SLinus Torvalds
71da177e4SLinus Torvaldsconfig MTD_PMC551
81da177e4SLinus Torvalds	tristate "Ramix PMC551 PCI Mezzanine RAM card support"
91da177e4SLinus Torvalds	depends on MTD && PCI
101da177e4SLinus Torvalds	---help---
111da177e4SLinus Torvalds	  This provides a MTD device driver for the Ramix PMC551 RAM PCI card
121da177e4SLinus Torvalds	  from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
131da177e4SLinus Torvalds	  These devices come in memory configurations from 32M - 1G.  If you
141da177e4SLinus Torvalds	  have one, you probably want to enable this.
151da177e4SLinus Torvalds
161da177e4SLinus Torvalds	  If this driver is compiled as a module you get the ability to select
171da177e4SLinus Torvalds	  the size of the aperture window pointing into the devices memory.
181da177e4SLinus Torvalds	  What this means is that if you have a 1G card, normally the kernel
191da177e4SLinus Torvalds	  will use a 1G memory map as its view of the device.  As a module,
201da177e4SLinus Torvalds	  you can select a 1M window into the memory and the driver will
211da177e4SLinus Torvalds	  "slide" the window around the PMC551's memory.  This was
221da177e4SLinus Torvalds	  particularly useful on the 2.2 kernels on PPC architectures as there
231da177e4SLinus Torvalds	  was limited kernel space to deal with.
241da177e4SLinus Torvalds
251da177e4SLinus Torvaldsconfig MTD_PMC551_BUGFIX
261da177e4SLinus Torvalds	bool "PMC551 256M DRAM Bugfix"
271da177e4SLinus Torvalds	depends on MTD_PMC551
281da177e4SLinus Torvalds	help
291da177e4SLinus Torvalds	  Some of Ramix's PMC551 boards with 256M configurations have invalid
301da177e4SLinus Torvalds	  column and row mux values.  This option will fix them, but will
311da177e4SLinus Torvalds	  break other memory configurations.  If unsure say N.
321da177e4SLinus Torvalds
331da177e4SLinus Torvaldsconfig MTD_PMC551_DEBUG
341da177e4SLinus Torvalds	bool "PMC551 Debugging"
351da177e4SLinus Torvalds	depends on MTD_PMC551
361da177e4SLinus Torvalds	help
371da177e4SLinus Torvalds	  This option makes the PMC551 more verbose during its operation and
381da177e4SLinus Torvalds	  is only really useful if you are developing on this driver or
391da177e4SLinus Torvalds	  suspect a possible hardware or driver bug.  If unsure say N.
401da177e4SLinus Torvalds
411da177e4SLinus Torvaldsconfig MTD_MS02NV
421da177e4SLinus Torvalds	tristate "DEC MS02-NV NVRAM module support"
431da177e4SLinus Torvalds	depends on MTD && MACH_DECSTATION
441da177e4SLinus Torvalds	help
451da177e4SLinus Torvalds	  This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
461da177e4SLinus Torvalds	  backed-up NVRAM module.  The module was originally meant as an NFS
471da177e4SLinus Torvalds	  accelerator.  Say Y here if you have a DECstation 5000/2x0 or a
481da177e4SLinus Torvalds	  DECsystem 5900 equipped with such a module.
491da177e4SLinus Torvalds
50*1d6432feSDavid Brownellconfig MTD_DATAFLASH
51*1d6432feSDavid Brownell	tristate "Support for AT45xxx DataFlash"
52*1d6432feSDavid Brownell	depends on MTD && SPI_MASTER && EXPERIMENTAL
53*1d6432feSDavid Brownell	help
54*1d6432feSDavid Brownell	  This enables access to AT45xxx DataFlash chips, using SPI.
55*1d6432feSDavid Brownell	  Sometimes DataFlash chips are packaged inside MMC-format
56*1d6432feSDavid Brownell	  cards; at this writing, the MMC stack won't handle those.
57*1d6432feSDavid Brownell
581da177e4SLinus Torvaldsconfig MTD_SLRAM
591da177e4SLinus Torvalds	tristate "Uncached system RAM"
601da177e4SLinus Torvalds	depends on MTD
611da177e4SLinus Torvalds	help
621da177e4SLinus Torvalds	  If your CPU cannot cache all of the physical memory in your machine,
631da177e4SLinus Torvalds	  you can still use it for storage or swap by using this driver to
641da177e4SLinus Torvalds	  present it to the system as a Memory Technology Device.
651da177e4SLinus Torvalds
661da177e4SLinus Torvaldsconfig MTD_PHRAM
671da177e4SLinus Torvalds	tristate "Physical system RAM"
681da177e4SLinus Torvalds	depends on MTD
691da177e4SLinus Torvalds	help
701da177e4SLinus Torvalds	  This is a re-implementation of the slram driver above.
711da177e4SLinus Torvalds
721da177e4SLinus Torvalds	  Use this driver to access physical memory that the kernel proper
731da177e4SLinus Torvalds	  doesn't have access to, memory beyond the mem=xxx limit, nvram,
741da177e4SLinus Torvalds	  memory on the video card, etc...
751da177e4SLinus Torvalds
761da177e4SLinus Torvaldsconfig MTD_LART
771da177e4SLinus Torvalds	tristate "28F160xx flash driver for LART"
781da177e4SLinus Torvalds	depends on SA1100_LART && MTD
791da177e4SLinus Torvalds	help
801da177e4SLinus Torvalds	  This enables the flash driver for LART. Please note that you do
811da177e4SLinus Torvalds	  not need any mapping/chip driver for LART. This one does it all
821da177e4SLinus Torvalds	  for you, so go disable all of those if you enabled some of them (:
831da177e4SLinus Torvalds
841da177e4SLinus Torvaldsconfig MTD_MTDRAM
851da177e4SLinus Torvalds	tristate "Test driver using RAM"
861da177e4SLinus Torvalds	depends on MTD
871da177e4SLinus Torvalds	help
881da177e4SLinus Torvalds	  This enables a test MTD device driver which uses vmalloc() to
891da177e4SLinus Torvalds	  provide storage.  You probably want to say 'N' unless you're
901da177e4SLinus Torvalds	  testing stuff.
911da177e4SLinus Torvalds
921da177e4SLinus Torvaldsconfig MTDRAM_TOTAL_SIZE
931da177e4SLinus Torvalds	int "MTDRAM device size in KiB"
941da177e4SLinus Torvalds	depends on MTD_MTDRAM
951da177e4SLinus Torvalds	default "4096"
961da177e4SLinus Torvalds	help
971da177e4SLinus Torvalds	  This allows you to configure the total size of the MTD device
981da177e4SLinus Torvalds	  emulated by the MTDRAM driver.  If the MTDRAM driver is built
991da177e4SLinus Torvalds	  as a module, it is also possible to specify this as a parameter when
1001da177e4SLinus Torvalds	  loading the module.
1011da177e4SLinus Torvalds
1021da177e4SLinus Torvaldsconfig MTDRAM_ERASE_SIZE
1031da177e4SLinus Torvalds	int "MTDRAM erase block size in KiB"
1041da177e4SLinus Torvalds	depends on MTD_MTDRAM
1051da177e4SLinus Torvalds	default "128"
1061da177e4SLinus Torvalds	help
1071da177e4SLinus Torvalds	  This allows you to configure the size of the erase blocks in the
1081da177e4SLinus Torvalds	  device emulated by the MTDRAM driver.  If the MTDRAM driver is built
1091da177e4SLinus Torvalds	  as a module, it is also possible to specify this as a parameter when
1101da177e4SLinus Torvalds	  loading the module.
1111da177e4SLinus Torvalds
1121da177e4SLinus Torvalds#If not a module (I don't want to test it as a module)
1131da177e4SLinus Torvaldsconfig MTDRAM_ABS_POS
1141da177e4SLinus Torvalds	hex "SRAM Hexadecimal Absolute position or 0"
1151da177e4SLinus Torvalds	depends on MTD_MTDRAM=y
1161da177e4SLinus Torvalds	default "0"
1171da177e4SLinus Torvalds	help
1181da177e4SLinus Torvalds	  If you have system RAM accessible by the CPU but not used by Linux
1191da177e4SLinus Torvalds	  in normal operation, you can give the physical address at which the
1201da177e4SLinus Torvalds	  available RAM starts, and the MTDRAM driver will use it instead of
1211da177e4SLinus Torvalds	  allocating space from Linux's available memory. Otherwise, leave
1221da177e4SLinus Torvalds	  this set to zero. Most people will want to leave this as zero.
1231da177e4SLinus Torvalds
1241da177e4SLinus Torvaldsconfig MTD_BLKMTD
1251da177e4SLinus Torvalds	tristate "MTD emulation using block device"
1261da177e4SLinus Torvalds	depends on MTD
1271da177e4SLinus Torvalds	help
1281da177e4SLinus Torvalds	  This driver allows a block device to appear as an MTD. It would
1291da177e4SLinus Torvalds	  generally be used in the following cases:
1301da177e4SLinus Torvalds
1311da177e4SLinus Torvalds	  Using Compact Flash as an MTD, these usually present themselves to
1321da177e4SLinus Torvalds	  the system as an ATA drive.
1331da177e4SLinus Torvalds	  Testing MTD users (eg JFFS2) on large media and media that might
1341da177e4SLinus Torvalds	  be removed during a write (using the floppy drive).
1351da177e4SLinus Torvalds
1361da177e4SLinus Torvaldsconfig MTD_BLOCK2MTD
1371da177e4SLinus Torvalds	tristate "MTD using block device (rewrite)"
1381da177e4SLinus Torvalds	depends on MTD && EXPERIMENTAL
1391da177e4SLinus Torvalds	help
1401da177e4SLinus Torvalds	  This driver is basically the same at MTD_BLKMTD above, but
1411da177e4SLinus Torvalds	  experienced some interface changes plus serious speedups.  In
1421da177e4SLinus Torvalds	  the long term, it should replace MTD_BLKMTD.  Right now, you
1431da177e4SLinus Torvalds	  shouldn't entrust important data to it yet.
1441da177e4SLinus Torvalds
1451da177e4SLinus Torvaldscomment "Disk-On-Chip Device Drivers"
1461da177e4SLinus Torvalds
1471da177e4SLinus Torvaldsconfig MTD_DOC2000
1481da177e4SLinus Torvalds	tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
1491da177e4SLinus Torvalds	depends on MTD
1501da177e4SLinus Torvalds	select MTD_DOCPROBE
1511da177e4SLinus Torvalds	select MTD_NAND_IDS
1521da177e4SLinus Torvalds	---help---
1531da177e4SLinus Torvalds	  This provides an MTD device driver for the M-Systems DiskOnChip
1541da177e4SLinus Torvalds	  2000 and Millennium devices.  Originally designed for the DiskOnChip
1551da177e4SLinus Torvalds	  2000, it also now includes support for the DiskOnChip Millennium.
1561da177e4SLinus Torvalds	  If you have problems with this driver and the DiskOnChip Millennium,
1571da177e4SLinus Torvalds	  you may wish to try the alternative Millennium driver below. To use
1581da177e4SLinus Torvalds	  the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
1591da177e4SLinus Torvalds	  in the <file:drivers/mtd/devices/docprobe.c> source code.
1601da177e4SLinus Torvalds
1611da177e4SLinus Torvalds	  If you use this device, you probably also want to enable the NFTL
1621da177e4SLinus Torvalds	  'NAND Flash Translation Layer' option below, which is used to
1631da177e4SLinus Torvalds	  emulate a block device by using a kind of file system on the flash
1641da177e4SLinus Torvalds	  chips.
1651da177e4SLinus Torvalds
1661da177e4SLinus Torvalds	  NOTE: This driver is deprecated and will probably be removed soon.
1671da177e4SLinus Torvalds	  Please try the new DiskOnChip driver under "NAND Flash Device
1681da177e4SLinus Torvalds	  Drivers".
1691da177e4SLinus Torvalds
1701da177e4SLinus Torvaldsconfig MTD_DOC2001
1711da177e4SLinus Torvalds	tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
1721da177e4SLinus Torvalds	depends on MTD
1731da177e4SLinus Torvalds	select MTD_DOCPROBE
1741da177e4SLinus Torvalds	select MTD_NAND_IDS
1751da177e4SLinus Torvalds	---help---
1761da177e4SLinus Torvalds	  This provides an alternative MTD device driver for the M-Systems
1771da177e4SLinus Torvalds	  DiskOnChip Millennium devices.  Use this if you have problems with
1781da177e4SLinus Torvalds	  the combined DiskOnChip 2000 and Millennium driver above.  To get
1791da177e4SLinus Torvalds	  the DiskOnChip probe code to load and use this driver instead of
1801da177e4SLinus Torvalds	  the other one, you will need to undefine DOC_SINGLE_DRIVER near
1811da177e4SLinus Torvalds	  the beginning of <file:drivers/mtd/devices/docprobe.c>.
1821da177e4SLinus Torvalds
1831da177e4SLinus Torvalds	  If you use this device, you probably also want to enable the NFTL
1841da177e4SLinus Torvalds	  'NAND Flash Translation Layer' option below, which is used to
1851da177e4SLinus Torvalds	  emulate a block device by using a kind of file system on the flash
1861da177e4SLinus Torvalds	  chips.
1871da177e4SLinus Torvalds
1881da177e4SLinus Torvalds	  NOTE: This driver is deprecated and will probably be removed soon.
1891da177e4SLinus Torvalds	  Please try the new DiskOnChip driver under "NAND Flash Device
1901da177e4SLinus Torvalds	  Drivers".
1911da177e4SLinus Torvalds
1921da177e4SLinus Torvaldsconfig MTD_DOC2001PLUS
1931da177e4SLinus Torvalds	tristate "M-Systems Disk-On-Chip Millennium Plus"
1941da177e4SLinus Torvalds	depends on MTD
1951da177e4SLinus Torvalds	select MTD_DOCPROBE
1961da177e4SLinus Torvalds	select MTD_NAND_IDS
1971da177e4SLinus Torvalds	---help---
1981da177e4SLinus Torvalds	  This provides an MTD device driver for the M-Systems DiskOnChip
1991da177e4SLinus Torvalds	  Millennium Plus devices.
2001da177e4SLinus Torvalds
2011da177e4SLinus Torvalds	  If you use this device, you probably also want to enable the INFTL
2021da177e4SLinus Torvalds	  'Inverse NAND Flash Translation Layer' option below, which is used
2031da177e4SLinus Torvalds	  to emulate a block device by using a kind of file system on the
2041da177e4SLinus Torvalds	  flash chips.
2051da177e4SLinus Torvalds
2061da177e4SLinus Torvalds	  NOTE: This driver will soon be replaced by the new DiskOnChip driver
2071da177e4SLinus Torvalds	  under "NAND Flash Device Drivers" (currently that driver does not
2081da177e4SLinus Torvalds	  support all Millennium Plus devices).
2091da177e4SLinus Torvalds
2101da177e4SLinus Torvaldsconfig MTD_DOCPROBE
2111da177e4SLinus Torvalds	tristate
2121da177e4SLinus Torvalds	select MTD_DOCECC
2131da177e4SLinus Torvalds
2141da177e4SLinus Torvaldsconfig MTD_DOCECC
2151da177e4SLinus Torvalds	tristate
2161da177e4SLinus Torvalds
2171da177e4SLinus Torvaldsconfig MTD_DOCPROBE_ADVANCED
2181da177e4SLinus Torvalds	bool "Advanced detection options for DiskOnChip"
2191da177e4SLinus Torvalds	depends on MTD_DOCPROBE
2201da177e4SLinus Torvalds	help
2211da177e4SLinus Torvalds	  This option allows you to specify nonstandard address at which to
2221da177e4SLinus Torvalds	  probe for a DiskOnChip, or to change the detection options.  You
2231da177e4SLinus Torvalds	  are unlikely to need any of this unless you are using LinuxBIOS.
2241da177e4SLinus Torvalds	  Say 'N'.
2251da177e4SLinus Torvalds
2261da177e4SLinus Torvaldsconfig MTD_DOCPROBE_ADDRESS
2271da177e4SLinus Torvalds	hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
2281da177e4SLinus Torvalds	depends on MTD_DOCPROBE
2291da177e4SLinus Torvalds	default "0x0000" if MTD_DOCPROBE_ADVANCED
2301da177e4SLinus Torvalds	default "0" if !MTD_DOCPROBE_ADVANCED
2311da177e4SLinus Torvalds	---help---
2321da177e4SLinus Torvalds	  By default, the probe for DiskOnChip devices will look for a
2331da177e4SLinus Torvalds	  DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
2341da177e4SLinus Torvalds	  This option allows you to specify a single address at which to probe
2351da177e4SLinus Torvalds	  for the device, which is useful if you have other devices in that
2361da177e4SLinus Torvalds	  range which get upset when they are probed.
2371da177e4SLinus Torvalds
2381da177e4SLinus Torvalds	  (Note that on PowerPC, the normal probe will only check at
2391da177e4SLinus Torvalds	  0xE4000000.)
2401da177e4SLinus Torvalds
2411da177e4SLinus Torvalds	  Normally, you should leave this set to zero, to allow the probe at
2421da177e4SLinus Torvalds	  the normal addresses.
2431da177e4SLinus Torvalds
2441da177e4SLinus Torvaldsconfig MTD_DOCPROBE_HIGH
2451da177e4SLinus Torvalds	bool "Probe high addresses"
2461da177e4SLinus Torvalds	depends on MTD_DOCPROBE_ADVANCED
2471da177e4SLinus Torvalds	help
2481da177e4SLinus Torvalds	  By default, the probe for DiskOnChip devices will look for a
2491da177e4SLinus Torvalds	  DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
2501da177e4SLinus Torvalds	  This option changes to make it probe between 0xFFFC8000 and
2511da177e4SLinus Torvalds	  0xFFFEE000.  Unless you are using LinuxBIOS, this is unlikely to be
2521da177e4SLinus Torvalds	  useful to you.  Say 'N'.
2531da177e4SLinus Torvalds
2541da177e4SLinus Torvaldsconfig MTD_DOCPROBE_55AA
2551da177e4SLinus Torvalds	bool "Probe for 0x55 0xAA BIOS Extension Signature"
2561da177e4SLinus Torvalds	depends on MTD_DOCPROBE_ADVANCED
2571da177e4SLinus Torvalds	help
2581da177e4SLinus Torvalds	  Check for the 0x55 0xAA signature of a DiskOnChip, and do not
2591da177e4SLinus Torvalds	  continue with probing if it is absent.  The signature will always be
2601da177e4SLinus Torvalds	  present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
2611da177e4SLinus Torvalds	  Only if you have overwritten the first block of a DiskOnChip
2621da177e4SLinus Torvalds	  Millennium will it be absent.  Enable this option if you are using
2631da177e4SLinus Torvalds	  LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
2641da177e4SLinus Torvalds	  you have managed to wipe the first block.
2651da177e4SLinus Torvalds
2661da177e4SLinus Torvaldsendmenu
2671da177e4SLinus Torvalds
268