[mirror_ubuntu-artful-kernel.git] / drivers / mtd / devices / Kconfig

menu "Self-contained MTD device drivers"
	depends on MTD!=n
	depends on HAS_IOMEM

config MTD_PMC551
	tristate "Ramix PMC551 PCI Mezzanine RAM card support"
	depends on PCI
	---help---
	  This provides a MTD device driver for the Ramix PMC551 RAM PCI card
	  from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
	  These devices come in memory configurations from 32M - 1G.  If you
	  have one, you probably want to enable this.

	  If this driver is compiled as a module you get the ability to select
	  the size of the aperture window pointing into the devices memory.
	  What this means is that if you have a 1G card, normally the kernel
	  will use a 1G memory map as its view of the device.  As a module,
	  you can select a 1M window into the memory and the driver will
	  "slide" the window around the PMC551's memory.  This was
	  particularly useful on the 2.2 kernels on PPC architectures as there
	  was limited kernel space to deal with.

config MTD_PMC551_BUGFIX
	bool "PMC551 256M DRAM Bugfix"
	depends on MTD_PMC551
	help
	  Some of Ramix's PMC551 boards with 256M configurations have invalid
	  column and row mux values.  This option will fix them, but will
	  break other memory configurations.  If unsure say N.

config MTD_PMC551_DEBUG
	bool "PMC551 Debugging"
	depends on MTD_PMC551
	help
	  This option makes the PMC551 more verbose during its operation and
	  is only really useful if you are developing on this driver or
	  suspect a possible hardware or driver bug.  If unsure say N.

config MTD_MS02NV
	tristate "DEC MS02-NV NVRAM module support"
	depends on MACH_DECSTATION
	help
	  This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
	  backed-up NVRAM module.  The module was originally meant as an NFS
	  accelerator.  Say Y here if you have a DECstation 5000/2x0 or a
	  DECsystem 5900 equipped with such a module.

	  If you want to compile this driver as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want),
	  say M here and read <file:Documentation/kbuild/modules.txt>.
	  The module will be called ms02-nv.

config MTD_DATAFLASH
	tristate "Support for AT45xxx DataFlash"
	depends on SPI_MASTER
	help
	  This enables access to AT45xxx DataFlash chips, using SPI.
	  Sometimes DataFlash chips are packaged inside MMC-format
	  cards; at this writing, the MMC stack won't handle those.

config MTD_DATAFLASH_WRITE_VERIFY
	bool "Verify DataFlash page writes"
	depends on MTD_DATAFLASH
	help
	  This adds an extra check when data is written to the flash.
	  It may help if you are verifying chip setup (timings etc) on
	  your board.  There is a rare possibility that even though the
	  device thinks the write was successful, a bit could have been
	  flipped accidentally due to device wear or something else.

config MTD_DATAFLASH_OTP
	bool "DataFlash OTP support (Security Register)"
	depends on MTD_DATAFLASH
	help
	  Newer DataFlash chips (revisions C and D) support 128 bytes of
	  one-time-programmable (OTP) data.  The first half may be written
	  (once) with up to 64 bytes of data, such as a serial number or
	  other key product data.  The second half is programmed with a
	  unique-to-each-chip bit pattern at the factory.

config MTD_M25P80
	tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
	depends on SPI_MASTER && MTD_SPI_NOR
	help
	  This enables access to most modern SPI flash chips, used for
	  program and data storage.   Series supported include Atmel AT26DF,
	  Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X.  Other chips
	  are supported as well.  See the driver source for the current list,
	  or to add other chips.

	  Note that the original DataFlash chips (AT45 series, not AT26DF),
	  need an entirely different driver.

	  Set up your spi devices with the right board-specific platform data,
	  if you want to specify device partitioning or to use a device which
	  doesn't support the JEDEC ID instruction.

config MTD_MCHP23K256
	tristate "Microchip 23K256 SRAM"
	depends on SPI_MASTER
	help
	  This enables access to Microchip 23K256 SRAM chips, using SPI.

	  Set up your spi devices with the right board-specific
	  platform data, or a device tree description if you want to
	  specify device partitioning

config MTD_SPEAR_SMI
	tristate "SPEAR MTD NOR Support through SMI controller"
	depends on PLAT_SPEAR
	default y
	help
	  This enable SNOR support on SPEAR platforms using SMI controller

config MTD_SST25L
	tristate "Support SST25L (non JEDEC) SPI Flash chips"
	depends on SPI_MASTER
	help
	  This enables access to the non JEDEC SST25L SPI flash chips, used
	  for program and data storage.

	  Set up your spi devices with the right board-specific platform data,
	  if you want to specify device partitioning.

config MTD_BCM47XXSFLASH
	tristate "Support for serial flash on BCMA bus"
	depends on BCMA_SFLASH && (MIPS || ARM)
	help
	  BCMA bus can have various flash memories attached, they are
	  registered by bcma as platform devices. This enables driver for
	  serial flash memories.

config MTD_SLRAM
	tristate "Uncached system RAM"
	help
	  If your CPU cannot cache all of the physical memory in your machine,
	  you can still use it for storage or swap by using this driver to
	  present it to the system as a Memory Technology Device.

config MTD_PHRAM
	tristate "Physical system RAM"
	help
	  This is a re-implementation of the slram driver above.

	  Use this driver to access physical memory that the kernel proper
	  doesn't have access to, memory beyond the mem=xxx limit, nvram,
	  memory on the video card, etc...

config MTD_LART
	tristate "28F160xx flash driver for LART"
	depends on SA1100_LART
	help
	  This enables the flash driver for LART. Please note that you do
	  not need any mapping/chip driver for LART. This one does it all
	  for you, so go disable all of those if you enabled some of them (:

config MTD_MTDRAM
	tristate "Test driver using RAM"
	help
	  This enables a test MTD device driver which uses vmalloc() to
	  provide storage.  You probably want to say 'N' unless you're
	  testing stuff.

config MTDRAM_TOTAL_SIZE
	int "MTDRAM device size in KiB"
	depends on MTD_MTDRAM
	default "4096"
	help
	  This allows you to configure the total size of the MTD device
	  emulated by the MTDRAM driver.  If the MTDRAM driver is built
	  as a module, it is also possible to specify this as a parameter when
	  loading the module.

config MTDRAM_ERASE_SIZE
	int "MTDRAM erase block size in KiB"
	depends on MTD_MTDRAM
	default "128"
	help
	  This allows you to configure the size of the erase blocks in the
	  device emulated by the MTDRAM driver.  If the MTDRAM driver is built
	  as a module, it is also possible to specify this as a parameter when
	  loading the module.

config MTD_BLOCK2MTD
	tristate "MTD using block device"
	depends on BLOCK
	help
	  This driver allows a block device to appear as an MTD. It would
	  generally be used in the following cases:

	  Using Compact Flash as an MTD, these usually present themselves to
	  the system as an ATA drive.
	  Testing MTD users (eg JFFS2) on large media and media that might
	  be removed during a write (using the floppy drive).

config MTD_POWERNV_FLASH
	tristate "powernv flash MTD driver"
	depends on PPC_POWERNV
	help
	  This provides an MTD device to access flash on powernv OPAL
	  platforms from Linux. This device abstracts away the
	  firmware interface for flash access.

comment "Disk-On-Chip Device Drivers"

config MTD_DOCG3
	tristate "M-Systems Disk-On-Chip G3"
	select BCH
	select BCH_CONST_PARAMS
	select BITREVERSE
	---help---
	  This provides an MTD device driver for the M-Systems DiskOnChip
	  G3 devices.

	  The driver provides access to G3 DiskOnChip, distributed by
	  M-Systems and now Sandisk. The support is very experimental,
	  and doesn't give access to any write operations.

config MTD_ST_SPI_FSM
	tristate "ST Microelectronics SPI FSM Serial Flash Controller"
	depends on ARCH_STI
	help
	  This provides an MTD device driver for the ST Microelectronics
	  SPI Fast Sequence Mode (FSM) Serial Flash Controller and support
	  for a subset of connected Serial Flash devices.

if MTD_DOCG3
config BCH_CONST_M
	default 14
config BCH_CONST_T
	default 4
endif

endmenu
Commit	Line	Data
1da177e4 LT	1	menu "Self-contained MTD device drivers"
1da177e4 LT	2	depends on MTD!=n
9310da0b	3	depends on HAS_IOMEM
1da177e4 LT	4
	5	config MTD_PMC551
	6	tristate "Ramix PMC551 PCI Mezzanine RAM card support"
ec98c681	7	depends on PCI
1da177e4 LT	8	---help---
	9	This provides a MTD device driver for the Ramix PMC551 RAM PCI card
	10	from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
	11	These devices come in memory configurations from 32M - 1G. If you
	12	have one, you probably want to enable this.
	13
	14	If this driver is compiled as a module you get the ability to select
	15	the size of the aperture window pointing into the devices memory.
	16	What this means is that if you have a 1G card, normally the kernel
	17	will use a 1G memory map as its view of the device. As a module,
	18	you can select a 1M window into the memory and the driver will
	19	"slide" the window around the PMC551's memory. This was
	20	particularly useful on the 2.2 kernels on PPC architectures as there
	21	was limited kernel space to deal with.
	22
	23	config MTD_PMC551_BUGFIX
	24	bool "PMC551 256M DRAM Bugfix"
	25	depends on MTD_PMC551
	26	help
	27	Some of Ramix's PMC551 boards with 256M configurations have invalid
	28	column and row mux values. This option will fix them, but will
	29	break other memory configurations. If unsure say N.
	30
	31	config MTD_PMC551_DEBUG
	32	bool "PMC551 Debugging"
	33	depends on MTD_PMC551
	34	help
	35	This option makes the PMC551 more verbose during its operation and
	36	is only really useful if you are developing on this driver or
	37	suspect a possible hardware or driver bug. If unsure say N.
	38
	39	config MTD_MS02NV
	40	tristate "DEC MS02-NV NVRAM module support"
ec98c681	41	depends on MACH_DECSTATION
1da177e4 LT	42	help
	43	This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
	44	backed-up NVRAM module. The module was originally meant as an NFS
	45	accelerator. Say Y here if you have a DECstation 5000/2x0 or a
	46	DECsystem 5900 equipped with such a module.
	47
be21ce11 MM	48	If you want to compile this driver as a module ( = code which can be
be21ce11 MM	49	inserted in and removed from the running kernel whenever you want),
39f5fb30	50	say M here and read <file:Documentation/kbuild/modules.txt>.
4737f097	51	The module will be called ms02-nv.
be21ce11	52
1d6432fe DB	53	config MTD_DATAFLASH
1d6432fe DB	54	tristate "Support for AT45xxx DataFlash"
a11ed37c	55	depends on SPI_MASTER
1d6432fe DB	56	help
	57	This enables access to AT45xxx DataFlash chips, using SPI.
	58	Sometimes DataFlash chips are packaged inside MMC-format
	59	cards; at this writing, the MMC stack won't handle those.
	60
8c64038e DB	61	config MTD_DATAFLASH_WRITE_VERIFY
	62	bool "Verify DataFlash page writes"
	63	depends on MTD_DATAFLASH
	64	help
	65	This adds an extra check when data is written to the flash.
	66	It may help if you are verifying chip setup (timings etc) on
	67	your board. There is a rare possibility that even though the
	68	device thinks the write was successful, a bit could have been
	69	flipped accidentally due to device wear or something else.
	70
34a82443 DB	71	config MTD_DATAFLASH_OTP
	72	bool "DataFlash OTP support (Security Register)"
	73	depends on MTD_DATAFLASH
34a82443 DB	74	help
	75	Newer DataFlash chips (revisions C and D) support 128 bytes of
	76	one-time-programmable (OTP) data. The first half may be written
	77	(once) with up to 64 bytes of data, such as a serial number or
	78	other key product data. The second half is programmed with a
	79	unique-to-each-chip bit pattern at the factory.
	80
2f9f7628	81	config MTD_M25P80
fa0a8c71	82	tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
e43b2061	83	depends on SPI_MASTER && MTD_SPI_NOR
2f9f7628	84	help
fa0a8c71 DB	85	This enables access to most modern SPI flash chips, used for
	86	program and data storage. Series supported include Atmel AT26DF,
	87	Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X. Other chips
	88	are supported as well. See the driver source for the current list,
	89	or to add other chips.
	90
	91	Note that the original DataFlash chips (AT45 series, not AT26DF),
	92	need an entirely different driver.
	93
	94	Set up your spi devices with the right board-specific platform data,
	95	if you want to specify device partitioning or to use a device which
	96	doesn't support the JEDEC ID instruction.
2f9f7628	97
5dc17fa6 AL	98	config MTD_MCHP23K256
	99	tristate "Microchip 23K256 SRAM"
	100	depends on SPI_MASTER
	101	help
	102	This enables access to Microchip 23K256 SRAM chips, using SPI.
	103
	104	Set up your spi devices with the right board-specific
	105	platform data, or a device tree description if you want to
	106	specify device partitioning
	107
f18dbbb1 SH	108	config MTD_SPEAR_SMI
	109	tristate "SPEAR MTD NOR Support through SMI controller"
	110	depends on PLAT_SPEAR
	111	default y
	112	help
	113	This enable SNOR support on SPEAR platforms using SMI controller
	114
ec77e21b RM	115	config MTD_SST25L
	116	tristate "Support SST25L (non JEDEC) SPI Flash chips"
	117	depends on SPI_MASTER
	118	help
	119	This enables access to the non JEDEC SST25L SPI flash chips, used
	120	for program and data storage.
	121
	122	Set up your spi devices with the right board-specific platform data,
	123	if you want to specify device partitioning.
	124
5fe42d5b	125	config MTD_BCM47XXSFLASH
0a526341	126	tristate "Support for serial flash on BCMA bus"
efacc699	127	depends on BCMA_SFLASH && (MIPS \|\| ARM)
5fe42d5b RM	128	help
	129	BCMA bus can have various flash memories attached, they are
	130	registered by bcma as platform devices. This enables driver for
0a526341	131	serial flash memories.
5fe42d5b	132
1da177e4 LT	133	config MTD_SLRAM
1da177e4 LT	134	tristate "Uncached system RAM"
1da177e4 LT	135	help
	136	If your CPU cannot cache all of the physical memory in your machine,
	137	you can still use it for storage or swap by using this driver to
	138	present it to the system as a Memory Technology Device.
	139
	140	config MTD_PHRAM
	141	tristate "Physical system RAM"
1da177e4 LT	142	help
	143	This is a re-implementation of the slram driver above.
	144
	145	Use this driver to access physical memory that the kernel proper
	146	doesn't have access to, memory beyond the mem=xxx limit, nvram,
	147	memory on the video card, etc...
	148
	149	config MTD_LART
	150	tristate "28F160xx flash driver for LART"
ec98c681	151	depends on SA1100_LART
1da177e4 LT	152	help
	153	This enables the flash driver for LART. Please note that you do
	154	not need any mapping/chip driver for LART. This one does it all
	155	for you, so go disable all of those if you enabled some of them (:
	156
	157	config MTD_MTDRAM
	158	tristate "Test driver using RAM"
1da177e4 LT	159	help
	160	This enables a test MTD device driver which uses vmalloc() to
	161	provide storage. You probably want to say 'N' unless you're
	162	testing stuff.
	163
	164	config MTDRAM_TOTAL_SIZE
	165	int "MTDRAM device size in KiB"
	166	depends on MTD_MTDRAM
	167	default "4096"
	168	help
	169	This allows you to configure the total size of the MTD device
	170	emulated by the MTDRAM driver. If the MTDRAM driver is built
	171	as a module, it is also possible to specify this as a parameter when
	172	loading the module.
	173
	174	config MTDRAM_ERASE_SIZE
	175	int "MTDRAM erase block size in KiB"
	176	depends on MTD_MTDRAM
	177	default "128"
	178	help
	179	This allows you to configure the size of the erase blocks in the
	180	device emulated by the MTDRAM driver. If the MTDRAM driver is built
	181	as a module, it is also possible to specify this as a parameter when
	182	loading the module.
	183
acc8dadc JE	184	config MTD_BLOCK2MTD
acc8dadc JE	185	tristate "MTD using block device"
ec98c681	186	depends on BLOCK
1da177e4 LT	187	help
	188	This driver allows a block device to appear as an MTD. It would
	189	generally be used in the following cases:
	190
	191	Using Compact Flash as an MTD, these usually present themselves to
	192	the system as an ATA drive.
	193	Testing MTD users (eg JFFS2) on large media and media that might
	194	be removed during a write (using the floppy drive).
	195
1cbb4a1c CB	196	config MTD_POWERNV_FLASH
	197	tristate "powernv flash MTD driver"
	198	depends on PPC_POWERNV
	199	help
	200	This provides an MTD device to access flash on powernv OPAL
	201	platforms from Linux. This device abstracts away the
	202	firmware interface for flash access.
	203
1da177e4 LT	204	comment "Disk-On-Chip Device Drivers"
1da177e4 LT	205
efa2ca73 RJ	206	config MTD_DOCG3
efa2ca73 RJ	207	tristate "M-Systems Disk-On-Chip G3"
d13d19ec RJ	208	select BCH
d13d19ec RJ	209	select BCH_CONST_PARAMS
bf65aaa6	210	select BITREVERSE
efa2ca73 RJ	211	---help---
	212	This provides an MTD device driver for the M-Systems DiskOnChip
	213	G3 devices.
	214
	215	The driver provides access to G3 DiskOnChip, distributed by
	216	M-Systems and now Sandisk. The support is very experimental,
	217	and doesn't give access to any write operations.
	218
d90db4a0 LJ	219	config MTD_ST_SPI_FSM
d90db4a0 LJ	220	tristate "ST Microelectronics SPI FSM Serial Flash Controller"
dc002f99	221	depends on ARCH_STI
d90db4a0 LJ	222	help
	223	This provides an MTD device driver for the ST Microelectronics
	224	SPI Fast Sequence Mode (FSM) Serial Flash Controller and support
	225	for a subset of connected Serial Flash devices.
	226
d13d19ec RJ	227	if MTD_DOCG3
	228	config BCH_CONST_M
	229	default 14
	230	config BCH_CONST_T
	231	default 4
	232	endif
	233
1da177e4	234	endmenu