xref: /openbmc/linux/drivers/mtd/devices/Kconfig (revision 023e4163)
1menu "Self-contained MTD device drivers"
2	depends on MTD!=n
3	depends on HAS_IOMEM
4
5config MTD_PMC551
6	tristate "Ramix PMC551 PCI Mezzanine RAM card support"
7	depends on PCI
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
23config 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
31config 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
39config MTD_MS02NV
40	tristate "DEC MS02-NV NVRAM module support"
41	depends on MACH_DECSTATION
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
48	  If you want to compile this driver as a module ( = code which can be
49	  inserted in and removed from the running kernel whenever you want),
50	  say M here and read <file:Documentation/kbuild/modules.txt>.
51	  The module will be called ms02-nv.
52
53config MTD_DATAFLASH
54	tristate "Support for AT45xxx DataFlash"
55	depends on SPI_MASTER
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
61config 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
71config MTD_DATAFLASH_OTP
72	bool "DataFlash OTP support (Security Register)"
73	depends on MTD_DATAFLASH
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
81config MTD_M25P80
82	tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
83	depends on SPI_MASTER && MTD_SPI_NOR
84	select SPI_MEM
85	help
86	  This enables access to most modern SPI flash chips, used for
87	  program and data storage.   Series supported include Atmel AT26DF,
88	  Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X.  Other chips
89	  are supported as well.  See the driver source for the current list,
90	  or to add other chips.
91
92	  Note that the original DataFlash chips (AT45 series, not AT26DF),
93	  need an entirely different driver.
94
95	  Set up your spi devices with the right board-specific platform data,
96	  if you want to specify device partitioning or to use a device which
97	  doesn't support the JEDEC ID instruction.
98
99config MTD_MCHP23K256
100	tristate "Microchip 23K256 SRAM"
101	depends on SPI_MASTER
102	help
103	  This enables access to Microchip 23K256 SRAM chips, using SPI.
104
105	  Set up your spi devices with the right board-specific
106	  platform data, or a device tree description if you want to
107	  specify device partitioning
108
109config MTD_SPEAR_SMI
110	tristate "SPEAR MTD NOR Support through SMI controller"
111	depends on PLAT_SPEAR
112	default y
113	help
114	  This enable SNOR support on SPEAR platforms using SMI controller
115
116config MTD_SST25L
117	tristate "Support SST25L (non JEDEC) SPI Flash chips"
118	depends on SPI_MASTER
119	help
120	  This enables access to the non JEDEC SST25L SPI flash chips, used
121	  for program and data storage.
122
123	  Set up your spi devices with the right board-specific platform data,
124	  if you want to specify device partitioning.
125
126config MTD_BCM47XXSFLASH
127	tristate "Support for serial flash on BCMA bus"
128	depends on BCMA_SFLASH && (MIPS || ARM)
129	help
130	  BCMA bus can have various flash memories attached, they are
131	  registered by bcma as platform devices. This enables driver for
132	  serial flash memories.
133
134config MTD_SLRAM
135	tristate "Uncached system RAM"
136	help
137	  If your CPU cannot cache all of the physical memory in your machine,
138	  you can still use it for storage or swap by using this driver to
139	  present it to the system as a Memory Technology Device.
140
141config MTD_PHRAM
142	tristate "Physical system RAM"
143	help
144	  This is a re-implementation of the slram driver above.
145
146	  Use this driver to access physical memory that the kernel proper
147	  doesn't have access to, memory beyond the mem=xxx limit, nvram,
148	  memory on the video card, etc...
149
150config MTD_LART
151	tristate "28F160xx flash driver for LART"
152	depends on SA1100_LART
153	help
154	  This enables the flash driver for LART. Please note that you do
155	  not need any mapping/chip driver for LART. This one does it all
156	  for you, so go disable all of those if you enabled some of them (:
157
158config MTD_MTDRAM
159	tristate "Test driver using RAM"
160	help
161	  This enables a test MTD device driver which uses vmalloc() to
162	  provide storage.  You probably want to say 'N' unless you're
163	  testing stuff.
164
165config MTDRAM_TOTAL_SIZE
166	int "MTDRAM device size in KiB"
167	depends on MTD_MTDRAM
168	default "4096"
169	help
170	  This allows you to configure the total size of the MTD device
171	  emulated by the MTDRAM driver.  If the MTDRAM driver is built
172	  as a module, it is also possible to specify this as a parameter when
173	  loading the module.
174
175config MTDRAM_ERASE_SIZE
176	int "MTDRAM erase block size in KiB"
177	depends on MTD_MTDRAM
178	default "128"
179	help
180	  This allows you to configure the size of the erase blocks in the
181	  device emulated by the MTDRAM driver.  If the MTDRAM driver is built
182	  as a module, it is also possible to specify this as a parameter when
183	  loading the module.
184
185config MTD_BLOCK2MTD
186	tristate "MTD using block device"
187	depends on BLOCK
188	help
189	  This driver allows a block device to appear as an MTD. It would
190	  generally be used in the following cases:
191
192	  Using Compact Flash as an MTD, these usually present themselves to
193	  the system as an ATA drive.
194	  Testing MTD users (eg JFFS2) on large media and media that might
195	  be removed during a write (using the floppy drive).
196
197config MTD_POWERNV_FLASH
198	tristate "powernv flash MTD driver"
199	depends on PPC_POWERNV
200	help
201	  This provides an MTD device to access flash on powernv OPAL
202	  platforms from Linux. This device abstracts away the
203	  firmware interface for flash access.
204
205comment "Disk-On-Chip Device Drivers"
206
207config MTD_DOCG3
208	tristate "M-Systems Disk-On-Chip G3"
209	select BCH
210	select BCH_CONST_PARAMS if !MTD_NAND_BCH
211	select BITREVERSE
212	help
213	  This provides an MTD device driver for the M-Systems DiskOnChip
214	  G3 devices.
215
216	  The driver provides access to G3 DiskOnChip, distributed by
217	  M-Systems and now Sandisk. The support is very experimental,
218	  and doesn't give access to any write operations.
219
220config MTD_ST_SPI_FSM
221	tristate "ST Microelectronics SPI FSM Serial Flash Controller"
222	depends on ARCH_STI
223	help
224	  This provides an MTD device driver for the ST Microelectronics
225	  SPI Fast Sequence Mode (FSM) Serial Flash Controller and support
226	  for a subset of connected Serial Flash devices.
227
228if MTD_DOCG3
229config BCH_CONST_M
230	default 14
231config BCH_CONST_T
232	default 4
233endif
234
235endmenu
236