Kconfig - OpenGrok cross reference for /linux-5.10/drivers/mtd/devices/Kconfig

1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "Self-contained MTD device drivers"
3 	depends on MTD!=n
4 	depends on HAS_IOMEM
8 	depends on PCI
10 	  This provides a MTD device driver for the Ramix PMC551 RAM PCI card
12 	  These devices come in memory configurations from 32M - 1G.  If you
15 	  If this driver is compiled as a module you get the ability to select
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
21 	  particularly useful on the 2.2 kernels on PPC architectures as there
26 	depends on MTD_PMC551
34 	depends on MTD_PMC551
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.
41 	tristate "DEC MS02-NV NVRAM module support"
42 	depends on MACH_DECSTATION
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.
49 	  If you want to compile this driver as a module ( = code which can be
52 	  The module will be called ms02-nv.
56 	depends on SPI_MASTER
59 	  Sometimes DataFlash chips are packaged inside MMC-format
64 	depends on MTD_DATAFLASH
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
74 	depends on MTD_DATAFLASH
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.
84 	depends on SPI_MASTER
88 	  Set up your spi devices with the right board-specific
89 	  platform data, or a device tree description if you want to
94 	depends on PLAT_SPEAR || COMPILE_TEST
97 	  This enable SNOR support on SPEAR platforms using SMI controller
101 	depends on SPI_MASTER
106 	  Set up your spi devices with the right board-specific platform data,
110 	tristate "Support for serial flash on BCMA bus"
111 	depends on BCMA_SFLASH && (MIPS || ARM)
118 	tristate "Uncached system RAM"
122 	  present it to the system as a Memory Technology Device.
125 	tristate "Physical system RAM"
127 	  This is a re-implementation of the slram driver above.
131 	  memory on the video card, etc...
135 	depends on SA1100_LART
138 	  not need any mapping/chip driver for LART. This one does it all
144 	  This enables a test MTD device driver which uses vmalloc() to
150 	depends on MTD_MTDRAM
155 	  as a module, it is also possible to specify this as a parameter when
160 	depends on MTD_MTDRAM
165 	  as a module, it is also possible to specify this as a parameter when
170 	depends on BLOCK
172 	  This driver allows a block device to appear as an MTD. It would
176 	  the system as an ATA drive.
177 	  Testing MTD users (eg JFFS2) on large media and media that might
178 	  be removed during a write (using the floppy drive).
182 	depends on PPC_POWERNV
184 	  This provides an MTD device to access flash on powernv OPAL
188 comment "Disk-On-Chip Device Drivers"
191 	tristate "M-Systems Disk-On-Chip G3"
196 	  This provides an MTD device driver for the M-Systems DiskOnChip
200 	  M-Systems and now Sandisk. The support is very experimental,
205 	depends on ARCH_STI
209 	  for a subset of connected Serial Flash devices.