xref: /openbmc/linux/drivers/mtd/devices/Kconfig (revision 714c068228d3275da6d36f29e544f7e5ae648849)
11da177e4SLinus Torvaldsmenu "Self-contained MTD device drivers"
21da177e4SLinus Torvalds	depends on MTD!=n
39310da0bSRichard Weinberger	depends on HAS_IOMEM
41da177e4SLinus Torvalds
51da177e4SLinus Torvaldsconfig MTD_PMC551
61da177e4SLinus Torvalds	tristate "Ramix PMC551 PCI Mezzanine RAM card support"
7ec98c681SJan Engelhardt	depends on PCI
8a8222a84SBoris Brezillon	help
91da177e4SLinus Torvalds	  This provides a MTD device driver for the Ramix PMC551 RAM PCI card
101da177e4SLinus Torvalds	  from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
111da177e4SLinus Torvalds	  These devices come in memory configurations from 32M - 1G.  If you
121da177e4SLinus Torvalds	  have one, you probably want to enable this.
131da177e4SLinus Torvalds
141da177e4SLinus Torvalds	  If this driver is compiled as a module you get the ability to select
151da177e4SLinus Torvalds	  the size of the aperture window pointing into the devices memory.
161da177e4SLinus Torvalds	  What this means is that if you have a 1G card, normally the kernel
171da177e4SLinus Torvalds	  will use a 1G memory map as its view of the device.  As a module,
181da177e4SLinus Torvalds	  you can select a 1M window into the memory and the driver will
191da177e4SLinus Torvalds	  "slide" the window around the PMC551's memory.  This was
201da177e4SLinus Torvalds	  particularly useful on the 2.2 kernels on PPC architectures as there
211da177e4SLinus Torvalds	  was limited kernel space to deal with.
221da177e4SLinus Torvalds
231da177e4SLinus Torvaldsconfig MTD_PMC551_BUGFIX
241da177e4SLinus Torvalds	bool "PMC551 256M DRAM Bugfix"
251da177e4SLinus Torvalds	depends on MTD_PMC551
261da177e4SLinus Torvalds	help
271da177e4SLinus Torvalds	  Some of Ramix's PMC551 boards with 256M configurations have invalid
281da177e4SLinus Torvalds	  column and row mux values.  This option will fix them, but will
291da177e4SLinus Torvalds	  break other memory configurations.  If unsure say N.
301da177e4SLinus Torvalds
311da177e4SLinus Torvaldsconfig MTD_PMC551_DEBUG
321da177e4SLinus Torvalds	bool "PMC551 Debugging"
331da177e4SLinus Torvalds	depends on MTD_PMC551
341da177e4SLinus Torvalds	help
351da177e4SLinus Torvalds	  This option makes the PMC551 more verbose during its operation and
361da177e4SLinus Torvalds	  is only really useful if you are developing on this driver or
371da177e4SLinus Torvalds	  suspect a possible hardware or driver bug.  If unsure say N.
381da177e4SLinus Torvalds
391da177e4SLinus Torvaldsconfig MTD_MS02NV
401da177e4SLinus Torvalds	tristate "DEC MS02-NV NVRAM module support"
41ec98c681SJan Engelhardt	depends on MACH_DECSTATION
421da177e4SLinus Torvalds	help
431da177e4SLinus Torvalds	  This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
441da177e4SLinus Torvalds	  backed-up NVRAM module.  The module was originally meant as an NFS
451da177e4SLinus Torvalds	  accelerator.  Say Y here if you have a DECstation 5000/2x0 or a
461da177e4SLinus Torvalds	  DECsystem 5900 equipped with such a module.
471da177e4SLinus Torvalds
48be21ce11SMartin Michlmayr	  If you want to compile this driver as a module ( = code which can be
49be21ce11SMartin Michlmayr	  inserted in and removed from the running kernel whenever you want),
5039f5fb30SAlexander E. Patrakov	  say M here and read <file:Documentation/kbuild/modules.txt>.
514737f097SPavel Machek	  The module will be called ms02-nv.
52be21ce11SMartin Michlmayr
531d6432feSDavid Brownellconfig MTD_DATAFLASH
541d6432feSDavid Brownell	tristate "Support for AT45xxx DataFlash"
55a11ed37cSKees Cook	depends on SPI_MASTER
561d6432feSDavid Brownell	help
571d6432feSDavid Brownell	  This enables access to AT45xxx DataFlash chips, using SPI.
581d6432feSDavid Brownell	  Sometimes DataFlash chips are packaged inside MMC-format
591d6432feSDavid Brownell	  cards; at this writing, the MMC stack won't handle those.
601d6432feSDavid Brownell
618c64038eSDavid Brownellconfig MTD_DATAFLASH_WRITE_VERIFY
628c64038eSDavid Brownell	bool "Verify DataFlash page writes"
638c64038eSDavid Brownell	depends on MTD_DATAFLASH
648c64038eSDavid Brownell	help
658c64038eSDavid Brownell	  This adds an extra check when data is written to the flash.
668c64038eSDavid Brownell	  It may help if you are verifying chip setup (timings etc) on
678c64038eSDavid Brownell	  your board.  There is a rare possibility that even though the
688c64038eSDavid Brownell	  device thinks the write was successful, a bit could have been
698c64038eSDavid Brownell	  flipped accidentally due to device wear or something else.
708c64038eSDavid Brownell
7134a82443SDavid Brownellconfig MTD_DATAFLASH_OTP
7234a82443SDavid Brownell	bool "DataFlash OTP support (Security Register)"
7334a82443SDavid Brownell	depends on MTD_DATAFLASH
7434a82443SDavid Brownell	help
7534a82443SDavid Brownell	  Newer DataFlash chips (revisions C and D) support 128 bytes of
7634a82443SDavid Brownell	  one-time-programmable (OTP) data.  The first half may be written
7734a82443SDavid Brownell	  (once) with up to 64 bytes of data, such as a serial number or
7834a82443SDavid Brownell	  other key product data.  The second half is programmed with a
7934a82443SDavid Brownell	  unique-to-each-chip bit pattern at the factory.
8034a82443SDavid Brownell
812f9f7628SMike Lavenderconfig MTD_M25P80
82fa0a8c71SDavid Brownell	tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
83e43b2061SBrian Norris	depends on SPI_MASTER && MTD_SPI_NOR
844120f8d1SBoris Brezillon	select SPI_MEM
852f9f7628SMike Lavender	help
86fa0a8c71SDavid Brownell	  This enables access to most modern SPI flash chips, used for
87fa0a8c71SDavid Brownell	  program and data storage.   Series supported include Atmel AT26DF,
88fa0a8c71SDavid Brownell	  Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X.  Other chips
89fa0a8c71SDavid Brownell	  are supported as well.  See the driver source for the current list,
90fa0a8c71SDavid Brownell	  or to add other chips.
91fa0a8c71SDavid Brownell
92fa0a8c71SDavid Brownell	  Note that the original DataFlash chips (AT45 series, not AT26DF),
93fa0a8c71SDavid Brownell	  need an entirely different driver.
94fa0a8c71SDavid Brownell
95fa0a8c71SDavid Brownell	  Set up your spi devices with the right board-specific platform data,
96fa0a8c71SDavid Brownell	  if you want to specify device partitioning or to use a device which
97fa0a8c71SDavid Brownell	  doesn't support the JEDEC ID instruction.
982f9f7628SMike Lavender
995dc17fa6SAndrew Lunnconfig MTD_MCHP23K256
1005dc17fa6SAndrew Lunn	tristate "Microchip 23K256 SRAM"
1015dc17fa6SAndrew Lunn	depends on SPI_MASTER
1025dc17fa6SAndrew Lunn	help
1035dc17fa6SAndrew Lunn	  This enables access to Microchip 23K256 SRAM chips, using SPI.
1045dc17fa6SAndrew Lunn
1055dc17fa6SAndrew Lunn	  Set up your spi devices with the right board-specific
1065dc17fa6SAndrew Lunn	  platform data, or a device tree description if you want to
1075dc17fa6SAndrew Lunn	  specify device partitioning
1085dc17fa6SAndrew Lunn
109f18dbbb1SShiraz Hashimconfig MTD_SPEAR_SMI
110f18dbbb1SShiraz Hashim	tristate "SPEAR MTD NOR Support through SMI controller"
111f18dbbb1SShiraz Hashim	depends on PLAT_SPEAR
112f18dbbb1SShiraz Hashim	default y
113f18dbbb1SShiraz Hashim	help
114f18dbbb1SShiraz Hashim	  This enable SNOR support on SPEAR platforms using SMI controller
115f18dbbb1SShiraz Hashim
116ec77e21bSRyan Mallonconfig MTD_SST25L
117ec77e21bSRyan Mallon	tristate "Support SST25L (non JEDEC) SPI Flash chips"
118ec77e21bSRyan Mallon	depends on SPI_MASTER
119ec77e21bSRyan Mallon	help
120ec77e21bSRyan Mallon	  This enables access to the non JEDEC SST25L SPI flash chips, used
121ec77e21bSRyan Mallon	  for program and data storage.
122ec77e21bSRyan Mallon
123ec77e21bSRyan Mallon	  Set up your spi devices with the right board-specific platform data,
124ec77e21bSRyan Mallon	  if you want to specify device partitioning.
125ec77e21bSRyan Mallon
1265fe42d5bSRafał Miłeckiconfig MTD_BCM47XXSFLASH
1270a526341SRafał Miłecki	tristate "Support for serial flash on BCMA bus"
128efacc699SRafał Miłecki	depends on BCMA_SFLASH && (MIPS || ARM)
1295fe42d5bSRafał Miłecki	help
1305fe42d5bSRafał Miłecki	  BCMA bus can have various flash memories attached, they are
1315fe42d5bSRafał Miłecki	  registered by bcma as platform devices. This enables driver for
1320a526341SRafał Miłecki	  serial flash memories.
1335fe42d5bSRafał Miłecki
1341da177e4SLinus Torvaldsconfig MTD_SLRAM
1351da177e4SLinus Torvalds	tristate "Uncached system RAM"
1361da177e4SLinus Torvalds	help
1371da177e4SLinus Torvalds	  If your CPU cannot cache all of the physical memory in your machine,
1381da177e4SLinus Torvalds	  you can still use it for storage or swap by using this driver to
1391da177e4SLinus Torvalds	  present it to the system as a Memory Technology Device.
1401da177e4SLinus Torvalds
1411da177e4SLinus Torvaldsconfig MTD_PHRAM
1421da177e4SLinus Torvalds	tristate "Physical system RAM"
1431da177e4SLinus Torvalds	help
1441da177e4SLinus Torvalds	  This is a re-implementation of the slram driver above.
1451da177e4SLinus Torvalds
1461da177e4SLinus Torvalds	  Use this driver to access physical memory that the kernel proper
1471da177e4SLinus Torvalds	  doesn't have access to, memory beyond the mem=xxx limit, nvram,
1481da177e4SLinus Torvalds	  memory on the video card, etc...
1491da177e4SLinus Torvalds
1501da177e4SLinus Torvaldsconfig MTD_LART
1511da177e4SLinus Torvalds	tristate "28F160xx flash driver for LART"
152ec98c681SJan Engelhardt	depends on SA1100_LART
1531da177e4SLinus Torvalds	help
1541da177e4SLinus Torvalds	  This enables the flash driver for LART. Please note that you do
1551da177e4SLinus Torvalds	  not need any mapping/chip driver for LART. This one does it all
1561da177e4SLinus Torvalds	  for you, so go disable all of those if you enabled some of them (:
1571da177e4SLinus Torvalds
1581da177e4SLinus Torvaldsconfig MTD_MTDRAM
1591da177e4SLinus Torvalds	tristate "Test driver using RAM"
1601da177e4SLinus Torvalds	help
1611da177e4SLinus Torvalds	  This enables a test MTD device driver which uses vmalloc() to
1621da177e4SLinus Torvalds	  provide storage.  You probably want to say 'N' unless you're
1631da177e4SLinus Torvalds	  testing stuff.
1641da177e4SLinus Torvalds
1651da177e4SLinus Torvaldsconfig MTDRAM_TOTAL_SIZE
1661da177e4SLinus Torvalds	int "MTDRAM device size in KiB"
1671da177e4SLinus Torvalds	depends on MTD_MTDRAM
1681da177e4SLinus Torvalds	default "4096"
1691da177e4SLinus Torvalds	help
1701da177e4SLinus Torvalds	  This allows you to configure the total size of the MTD device
1711da177e4SLinus Torvalds	  emulated by the MTDRAM driver.  If the MTDRAM driver is built
1721da177e4SLinus Torvalds	  as a module, it is also possible to specify this as a parameter when
1731da177e4SLinus Torvalds	  loading the module.
1741da177e4SLinus Torvalds
1751da177e4SLinus Torvaldsconfig MTDRAM_ERASE_SIZE
1761da177e4SLinus Torvalds	int "MTDRAM erase block size in KiB"
1771da177e4SLinus Torvalds	depends on MTD_MTDRAM
1781da177e4SLinus Torvalds	default "128"
1791da177e4SLinus Torvalds	help
1801da177e4SLinus Torvalds	  This allows you to configure the size of the erase blocks in the
1811da177e4SLinus Torvalds	  device emulated by the MTDRAM driver.  If the MTDRAM driver is built
1821da177e4SLinus Torvalds	  as a module, it is also possible to specify this as a parameter when
1831da177e4SLinus Torvalds	  loading the module.
1841da177e4SLinus Torvalds
185acc8dadcSJoern Engelconfig MTD_BLOCK2MTD
186acc8dadcSJoern Engel	tristate "MTD using block device"
187ec98c681SJan Engelhardt	depends on BLOCK
1881da177e4SLinus Torvalds	help
1891da177e4SLinus Torvalds	  This driver allows a block device to appear as an MTD. It would
1901da177e4SLinus Torvalds	  generally be used in the following cases:
1911da177e4SLinus Torvalds
1921da177e4SLinus Torvalds	  Using Compact Flash as an MTD, these usually present themselves to
1931da177e4SLinus Torvalds	  the system as an ATA drive.
1941da177e4SLinus Torvalds	  Testing MTD users (eg JFFS2) on large media and media that might
1951da177e4SLinus Torvalds	  be removed during a write (using the floppy drive).
1961da177e4SLinus Torvalds
1971cbb4a1cSCyril Burconfig MTD_POWERNV_FLASH
1981cbb4a1cSCyril Bur	tristate "powernv flash MTD driver"
1991cbb4a1cSCyril Bur	depends on PPC_POWERNV
2001cbb4a1cSCyril Bur	help
2011cbb4a1cSCyril Bur	  This provides an MTD device to access flash on powernv OPAL
2021cbb4a1cSCyril Bur	  platforms from Linux. This device abstracts away the
2031cbb4a1cSCyril Bur	  firmware interface for flash access.
2041cbb4a1cSCyril Bur
2051da177e4SLinus Torvaldscomment "Disk-On-Chip Device Drivers"
2061da177e4SLinus Torvalds
207efa2ca73SRobert Jarzmikconfig MTD_DOCG3
208efa2ca73SRobert Jarzmik	tristate "M-Systems Disk-On-Chip G3"
209d13d19ecSRobert Jarzmik	select BCH
210*714c0682SMiquel Raynal	select BCH_CONST_PARAMS if !MTD_NAND_ECC_SW_BCH
211bf65aaa6SRobert Jarzmik	select BITREVERSE
212a8222a84SBoris Brezillon	help
213efa2ca73SRobert Jarzmik	  This provides an MTD device driver for the M-Systems DiskOnChip
214efa2ca73SRobert Jarzmik	  G3 devices.
215efa2ca73SRobert Jarzmik
216efa2ca73SRobert Jarzmik	  The driver provides access to G3 DiskOnChip, distributed by
217efa2ca73SRobert Jarzmik	  M-Systems and now Sandisk. The support is very experimental,
218efa2ca73SRobert Jarzmik	  and doesn't give access to any write operations.
219efa2ca73SRobert Jarzmik
220d90db4a0SLee Jonesconfig MTD_ST_SPI_FSM
221d90db4a0SLee Jones	tristate "ST Microelectronics SPI FSM Serial Flash Controller"
222dc002f99SBrian Norris	depends on ARCH_STI
223d90db4a0SLee Jones	help
224d90db4a0SLee Jones	  This provides an MTD device driver for the ST Microelectronics
225d90db4a0SLee Jones	  SPI Fast Sequence Mode (FSM) Serial Flash Controller and support
226d90db4a0SLee Jones	  for a subset of connected Serial Flash devices.
227d90db4a0SLee Jones
228d13d19ecSRobert Jarzmikif MTD_DOCG3
229d13d19ecSRobert Jarzmikconfig BCH_CONST_M
230d13d19ecSRobert Jarzmik	default 14
231d13d19ecSRobert Jarzmikconfig BCH_CONST_T
232d13d19ecSRobert Jarzmik	default 4
233d13d19ecSRobert Jarzmikendif
234d13d19ecSRobert Jarzmik
2351da177e4SLinus Torvaldsendmenu
236