[linux-2.6-block.git] / drivers / mtd / devices / Kconfig

# SPDX-License-Identifier: GPL-2.0-only
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
	select SPI_MEM
	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 if !MTD_NAND_ECC_SW_BCH
	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
ec8f24b7	1	# SPDX-License-Identifier: GPL-2.0-only
1da177e4 LT	2	menu "Self-contained MTD device drivers"
1da177e4 LT	3	depends on MTD!=n
9310da0b	4	depends on HAS_IOMEM
1da177e4 LT	5
	6	config MTD_PMC551
	7	tristate "Ramix PMC551 PCI Mezzanine RAM card support"
ec98c681	8	depends on PCI
a8222a84	9	help
1da177e4 LT	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"
ec98c681	42	depends on MACH_DECSTATION
1da177e4 LT	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
be21ce11 MM	49	If you want to compile this driver as a module ( = code which can be
be21ce11 MM	50	inserted in and removed from the running kernel whenever you want),
39f5fb30	51	say M here and read <file:Documentation/kbuild/modules.txt>.
4737f097	52	The module will be called ms02-nv.
be21ce11	53
1d6432fe DB	54	config MTD_DATAFLASH
1d6432fe DB	55	tristate "Support for AT45xxx DataFlash"
a11ed37c	56	depends on SPI_MASTER
1d6432fe DB	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
8c64038e DB	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
34a82443 DB	72	config MTD_DATAFLASH_OTP
	73	bool "DataFlash OTP support (Security Register)"
	74	depends on MTD_DATAFLASH
34a82443 DB	75	help
	76	Newer DataFlash chips (revisions C and D) support 128 bytes of
	77	one-time-programmable (OTP) data. The first half may be written
	78	(once) with up to 64 bytes of data, such as a serial number or
	79	other key product data. The second half is programmed with a
	80	unique-to-each-chip bit pattern at the factory.
	81
2f9f7628	82	config MTD_M25P80
fa0a8c71	83	tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
e43b2061	84	depends on SPI_MASTER && MTD_SPI_NOR
4120f8d1	85	select SPI_MEM
2f9f7628	86	help
fa0a8c71 DB	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.
2f9f7628	99
5dc17fa6 AL	100	config MTD_MCHP23K256
	101	tristate "Microchip 23K256 SRAM"
	102	depends on SPI_MASTER
	103	help
	104	This enables access to Microchip 23K256 SRAM chips, using SPI.
	105
	106	Set up your spi devices with the right board-specific
	107	platform data, or a device tree description if you want to
	108	specify device partitioning
	109
f18dbbb1 SH	110	config MTD_SPEAR_SMI
	111	tristate "SPEAR MTD NOR Support through SMI controller"
	112	depends on PLAT_SPEAR
	113	default y
	114	help
	115	This enable SNOR support on SPEAR platforms using SMI controller
	116
ec77e21b RM	117	config MTD_SST25L
	118	tristate "Support SST25L (non JEDEC) SPI Flash chips"
	119	depends on SPI_MASTER
	120	help
	121	This enables access to the non JEDEC SST25L SPI flash chips, used
	122	for program and data storage.
	123
	124	Set up your spi devices with the right board-specific platform data,
	125	if you want to specify device partitioning.
	126
5fe42d5b	127	config MTD_BCM47XXSFLASH
0a526341	128	tristate "Support for serial flash on BCMA bus"
efacc699	129	depends on BCMA_SFLASH && (MIPS \|\| ARM)
5fe42d5b RM	130	help
	131	BCMA bus can have various flash memories attached, they are
	132	registered by bcma as platform devices. This enables driver for
0a526341	133	serial flash memories.
5fe42d5b	134
1da177e4 LT	135	config MTD_SLRAM
1da177e4 LT	136	tristate "Uncached system RAM"
1da177e4 LT	137	help
	138	If your CPU cannot cache all of the physical memory in your machine,
	139	you can still use it for storage or swap by using this driver to
	140	present it to the system as a Memory Technology Device.
	141
	142	config MTD_PHRAM
	143	tristate "Physical system RAM"
1da177e4 LT	144	help
	145	This is a re-implementation of the slram driver above.
	146
	147	Use this driver to access physical memory that the kernel proper
	148	doesn't have access to, memory beyond the mem=xxx limit, nvram,
	149	memory on the video card, etc...
	150
	151	config MTD_LART
	152	tristate "28F160xx flash driver for LART"
ec98c681	153	depends on SA1100_LART
1da177e4 LT	154	help
	155	This enables the flash driver for LART. Please note that you do
	156	not need any mapping/chip driver for LART. This one does it all
	157	for you, so go disable all of those if you enabled some of them (:
	158
	159	config MTD_MTDRAM
	160	tristate "Test driver using RAM"
1da177e4 LT	161	help
	162	This enables a test MTD device driver which uses vmalloc() to
	163	provide storage. You probably want to say 'N' unless you're
	164	testing stuff.
	165
	166	config MTDRAM_TOTAL_SIZE
	167	int "MTDRAM device size in KiB"
	168	depends on MTD_MTDRAM
	169	default "4096"
	170	help
	171	This allows you to configure the total size of the MTD device
	172	emulated by the MTDRAM driver. If the MTDRAM driver is built
	173	as a module, it is also possible to specify this as a parameter when
	174	loading the module.
	175
	176	config MTDRAM_ERASE_SIZE
	177	int "MTDRAM erase block size in KiB"
	178	depends on MTD_MTDRAM
	179	default "128"
	180	help
	181	This allows you to configure the size of the erase blocks in the
	182	device emulated by the MTDRAM driver. If the MTDRAM driver is built
	183	as a module, it is also possible to specify this as a parameter when
	184	loading the module.
	185
acc8dadc JE	186	config MTD_BLOCK2MTD
acc8dadc JE	187	tristate "MTD using block device"
ec98c681	188	depends on BLOCK
1da177e4 LT	189	help
	190	This driver allows a block device to appear as an MTD. It would
	191	generally be used in the following cases:
	192
	193	Using Compact Flash as an MTD, these usually present themselves to
	194	the system as an ATA drive.
	195	Testing MTD users (eg JFFS2) on large media and media that might
	196	be removed during a write (using the floppy drive).
	197
1cbb4a1c CB	198	config MTD_POWERNV_FLASH
	199	tristate "powernv flash MTD driver"
	200	depends on PPC_POWERNV
	201	help
	202	This provides an MTD device to access flash on powernv OPAL
	203	platforms from Linux. This device abstracts away the
	204	firmware interface for flash access.
	205
1da177e4 LT	206	comment "Disk-On-Chip Device Drivers"
1da177e4 LT	207
efa2ca73 RJ	208	config MTD_DOCG3
efa2ca73 RJ	209	tristate "M-Systems Disk-On-Chip G3"
d13d19ec	210	select BCH
714c0682	211	select BCH_CONST_PARAMS if !MTD_NAND_ECC_SW_BCH
bf65aaa6	212	select BITREVERSE
a8222a84	213	help
efa2ca73 RJ	214	This provides an MTD device driver for the M-Systems DiskOnChip
	215	G3 devices.
	216
	217	The driver provides access to G3 DiskOnChip, distributed by
	218	M-Systems and now Sandisk. The support is very experimental,
	219	and doesn't give access to any write operations.
	220
d90db4a0 LJ	221	config MTD_ST_SPI_FSM
d90db4a0 LJ	222	tristate "ST Microelectronics SPI FSM Serial Flash Controller"
dc002f99	223	depends on ARCH_STI
d90db4a0 LJ	224	help
	225	This provides an MTD device driver for the ST Microelectronics
	226	SPI Fast Sequence Mode (FSM) Serial Flash Controller and support
	227	for a subset of connected Serial Flash devices.
	228
d13d19ec RJ	229	if MTD_DOCG3
	230	config BCH_CONST_M
	231	default 14
	232	config BCH_CONST_T
	233	default 4
	234	endif
	235
1da177e4	236	endmenu