xref: /openbmc/linux/drivers/mtd/maps/Kconfig (revision 367b8112)
1# drivers/mtd/maps/Kconfig
2
3menu "Mapping drivers for chip access"
4	depends on MTD!=n
5
6config MTD_COMPLEX_MAPPINGS
7	bool "Support non-linear mappings of flash chips"
8	help
9	  This causes the chip drivers to allow for complicated
10	  paged mappings of flash chips.
11
12config MTD_PHYSMAP
13	tristate "CFI Flash device in physical memory map"
14	depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM
15	help
16	  This provides a 'mapping' driver which allows the NOR Flash and
17	  ROM driver code to communicate with chips which are mapped
18	  physically into the CPU's memory. You will need to configure
19	  the physical address and size of the flash chips on your
20	  particular board as well as the bus width, either statically
21	  with config options or at run-time.
22
23	  To compile this driver as a module, choose M here: the
24	  module will be called physmap.
25
26config MTD_PHYSMAP_START
27	hex "Physical start address of flash mapping"
28	depends on MTD_PHYSMAP
29	default "0x8000000"
30	help
31	  This is the physical memory location at which the flash chips
32	  are mapped on your particular target board. Refer to the
33	  memory map which should hopefully be in the documentation for
34	  your board.
35	  Ignore this option if you use run-time physmap configuration
36	  (i.e., run-time calling physmap_configure()).
37
38config MTD_PHYSMAP_LEN
39	hex "Physical length of flash mapping"
40	depends on MTD_PHYSMAP
41	default "0"
42	help
43	  This is the total length of the mapping of the flash chips on
44	  your particular board. If there is space, or aliases, in the
45	  physical memory map between the chips, this could be larger
46	  than the total amount of flash present. Refer to the memory
47	  map which should hopefully be in the documentation for your
48	  board.
49	  Ignore this option if you use run-time physmap configuration
50	  (i.e., run-time calling physmap_configure()).
51
52config MTD_PHYSMAP_BANKWIDTH
53	int "Bank width in octets"
54	depends on MTD_PHYSMAP
55	default "2"
56	help
57	  This is the total width of the data bus of the flash devices
58	  in octets. For example, if you have a data bus width of 32
59	  bits, you would set the bus width octet value to 4. This is
60	  used internally by the CFI drivers.
61	  Ignore this option if you use run-time physmap configuration
62	  (i.e., run-time calling physmap_configure()).
63
64config MTD_PHYSMAP_OF
65	tristate "Flash device in physical memory map based on OF description"
66	depends on PPC_OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM)
67	help
68	  This provides a 'mapping' driver which allows the NOR Flash and
69	  ROM driver code to communicate with chips which are mapped
70	  physically into the CPU's memory. The mapping description here is
71	  taken from OF device tree.
72
73config MTD_PMC_MSP_EVM
74	tristate "CFI Flash device mapped on PMC-Sierra MSP"
75	depends on PMC_MSP && MTD_CFI
76	select MTD_PARTITIONS
77	help
78	  This provides a 'mapping' driver which supports the way
79	  in which user-programmable flash chips are connected on the
80	  PMC-Sierra MSP eval/demo boards.
81
82choice
83	prompt "Maximum mappable memory available for flash IO"
84	depends on MTD_PMC_MSP_EVM
85	default MSP_FLASH_MAP_LIMIT_32M
86
87config MSP_FLASH_MAP_LIMIT_32M
88	bool "32M"
89
90endchoice
91
92config MSP_FLASH_MAP_LIMIT
93	hex
94	default "0x02000000"
95	depends on MSP_FLASH_MAP_LIMIT_32M
96
97config MTD_PMC_MSP_RAMROOT
98	tristate "Embedded RAM block device for root on PMC-Sierra MSP"
99	depends on PMC_MSP_EMBEDDED_ROOTFS && \
100			(MTD_BLOCK || MTD_BLOCK_RO) && \
101			MTD_RAM
102	help
103	  This provides support for the embedded root file system
104          on PMC MSP devices.  This memory is mapped as a MTD block device.
105
106config MTD_SUN_UFLASH
107	tristate "Sun Microsystems userflash support"
108	depends on SPARC && MTD_CFI && PCI
109	help
110	  This provides a 'mapping' driver which supports the way in
111	  which user-programmable flash chips are connected on various
112	  Sun Microsystems boardsets.  This driver will require CFI support
113	  in the kernel, so if you did not enable CFI previously, do that now.
114
115config MTD_SC520CDP
116	tristate "CFI Flash device mapped on AMD SC520 CDP"
117	depends on X86 && MTD_CFI && MTD_CONCAT
118	help
119	  The SC520 CDP board has two banks of CFI-compliant chips and one
120	  Dual-in-line JEDEC chip. This 'mapping' driver supports that
121	  arrangement, implementing three MTD devices.
122
123config MTD_NETSC520
124	tristate "CFI Flash device mapped on AMD NetSc520"
125	depends on X86 && MTD_CFI && MTD_PARTITIONS
126	help
127	  This enables access routines for the flash chips on the AMD NetSc520
128	  demonstration board. If you have one of these boards and would like
129	  to use the flash chips on it, say 'Y'.
130
131config MTD_TS5500
132	tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"
133	depends on X86
134	select MTD_PARTITIONS
135	select MTD_JEDECPROBE
136	select MTD_CFI_AMDSTD
137	help
138	  This provides a driver for the on-board flash of the Technologic
139	  System's TS-5500 board. The 2MB flash is split into 3 partitions
140	  which are accessed as separate MTD devices.
141
142	  mtd0 and mtd2 are the two BIOS drives, which use the resident
143	  flash disk (RFD) flash translation layer.
144
145	  mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
146
147	  Note that jumper 3 ("Write Enable Drive A") must be set
148	  otherwise detection won't succeed.
149
150config MTD_SBC_GXX
151	tristate "CFI Flash device mapped on Arcom SBC-GXx boards"
152	depends on X86 && MTD_CFI_INTELEXT && MTD_PARTITIONS && MTD_COMPLEX_MAPPINGS
153	help
154	  This provides a driver for the on-board flash of Arcom Control
155	  Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
156	  By default the flash is split into 3 partitions which are accessed
157	  as separate MTD devices. This board utilizes Intel StrataFlash.
158	  More info at
159	  <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.
160
161config MTD_PXA2XX
162	tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"
163	depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT
164	select MTD_PARTITIONS
165	help
166	  This provides a driver for the NOR flash attached to a PXA2xx chip.
167
168config MTD_OCTAGON
169	tristate "JEDEC Flash device mapped on Octagon 5066 SBC"
170	depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
171	help
172	  This provides a 'mapping' driver which supports the way in which
173	  the flash chips are connected in the Octagon-5066 Single Board
174	  Computer. More information on the board is available at
175	  <http://www.octagonsystems.com/CPUpages/5066.html>.
176
177config MTD_VMAX
178	tristate "JEDEC Flash device mapped on Tempustech VMAX SBC301"
179	depends on X86 && MTD_JEDEC && MTD_COMPLEX_MAPPINGS
180	help
181	  This provides a 'mapping' driver which supports the way in which
182	  the flash chips are connected in the Tempustech VMAX SBC301 Single
183	  Board Computer. More information on the board is available at
184	  <http://www.tempustech.com/>.
185
186config MTD_SCx200_DOCFLASH
187	tristate "Flash device mapped with DOCCS on NatSemi SCx200"
188	depends on SCx200 && MTD_CFI && MTD_PARTITIONS
189	help
190	  Enable support for a flash chip mapped using the DOCCS signal on a
191	  National Semiconductor SCx200 processor.
192
193	  If you don't know what to do here, say N.
194
195	  If compiled as a module, it will be called scx200_docflash.
196
197config MTD_AMD76XROM
198	tristate "BIOS flash chip on AMD76x southbridge"
199	depends on X86 && MTD_JEDECPROBE
200	help
201	  Support for treating the BIOS flash chip on AMD76x motherboards
202	  as an MTD device - with this you can reprogram your BIOS.
203
204	  BE VERY CAREFUL.
205
206config MTD_ICHXROM
207	tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"
208	depends on X86 && MTD_JEDECPROBE
209	help
210	  Support for treating the BIOS flash chip on ICHX motherboards
211	  as an MTD device - with this you can reprogram your BIOS.
212
213	  BE VERY CAREFUL.
214
215config MTD_ESB2ROM
216        tristate "BIOS flash chip on Intel ESB Controller Hub 2"
217        depends on X86 && MTD_JEDECPROBE && PCI
218        help
219          Support for treating the BIOS flash chip on ESB2 motherboards
220          as an MTD device - with this you can reprogram your BIOS.
221
222          BE VERY CAREFUL.
223
224config MTD_CK804XROM
225	tristate "BIOS flash chip on Nvidia CK804"
226	depends on X86 && MTD_JEDECPROBE && PCI
227	help
228	  Support for treating the BIOS flash chip on nvidia motherboards
229	  as an MTD device - with this you can reprogram your BIOS.
230
231	  BE VERY CAREFUL.
232
233config MTD_SCB2_FLASH
234	tristate "BIOS flash chip on Intel SCB2 boards"
235	depends on X86 && MTD_JEDECPROBE
236	help
237	  Support for treating the BIOS flash chip on Intel SCB2 boards
238	  as an MTD device - with this you can reprogram your BIOS.
239
240	  BE VERY CAREFUL.
241
242config MTD_TSUNAMI
243	tristate "Flash chips on Tsunami TIG bus"
244	depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS
245	help
246	  Support for the flash chip on Tsunami TIG bus.
247
248config MTD_NETtel
249	tristate "CFI flash device on SnapGear/SecureEdge"
250	depends on X86 && MTD_PARTITIONS && MTD_JEDECPROBE
251	help
252	  Support for flash chips on NETtel/SecureEdge/SnapGear boards.
253
254config MTD_ALCHEMY
255	tristate "AMD Alchemy Pb1xxx/Db1xxx/RDK MTD support"
256	depends on SOC_AU1X00 && MTD_PARTITIONS && MTD_CFI
257	help
258	  Flash memory access on AMD Alchemy Pb/Db/RDK Reference Boards
259
260config MTD_DILNETPC
261	tristate "CFI Flash device mapped on DIL/Net PC"
262	depends on X86 && MTD_CONCAT && MTD_PARTITIONS && MTD_CFI_INTELEXT
263	help
264	  MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
265	  For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
266 	  and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
267
268config MTD_DILNETPC_BOOTSIZE
269	hex "Size of DIL/Net PC flash boot partition"
270	depends on MTD_DILNETPC
271	default "0x80000"
272	help
273	  The amount of space taken up by the kernel or Etherboot
274	  on the DIL/Net PC flash chips.
275
276config MTD_L440GX
277	tristate "BIOS flash chip on Intel L440GX boards"
278	depends on X86 && MTD_JEDECPROBE
279	help
280	  Support for treating the BIOS flash chip on Intel L440GX motherboards
281	  as an MTD device - with this you can reprogram your BIOS.
282
283	  BE VERY CAREFUL.
284
285config MTD_SBC8240
286	tristate "Flash device on SBC8240"
287	depends on MTD_JEDECPROBE && 8260
288	help
289          Flash access on the SBC8240 board from Wind River.  See
290          <http://www.windriver.com/products/sbc8240/>
291
292config MTD_TQM8XXL
293	tristate "CFI Flash device mapped on TQM8XXL"
294	depends on MTD_CFI && TQM8xxL
295	help
296	  The TQM8xxL PowerPC board has up to two banks of CFI-compliant
297	  chips, currently uses AMD one. This 'mapping' driver supports
298	  that arrangement, allowing the CFI probe and command set driver
299	  code to communicate with the chips on the TQM8xxL board. More at
300	  <http://www.denx.de/embedded-ppc-en.html>.
301
302config MTD_RPXLITE
303	tristate "CFI Flash device mapped on RPX Lite or CLLF"
304	depends on MTD_CFI && (RPXCLASSIC || RPXLITE)
305	help
306	  The RPXLite PowerPC board has CFI-compliant chips mapped in
307	  a strange sparse mapping. This 'mapping' driver supports that
308	  arrangement, allowing the CFI probe and command set driver code
309	  to communicate with the chips on the RPXLite board. More at
310	  <http://www.embeddedplanet.com/>.
311
312config MTD_MBX860
313	tristate "System flash on MBX860 board"
314	depends on MTD_CFI && MBX
315	help
316	  This enables access routines for the flash chips on the Motorola
317	  MBX860 board. If you have one of these boards and would like
318	  to use the flash chips on it, say 'Y'.
319
320config MTD_DBOX2
321	tristate "CFI Flash device mapped on D-Box2"
322	depends on DBOX2 && MTD_CFI_INTELSTD && MTD_CFI_INTELEXT && MTD_CFI_AMDSTD
323	help
324	  This enables access routines for the flash chips on the Nokia/Sagem
325	  D-Box 2 board. If you have one of these boards and would like to use
326	  the flash chips on it, say 'Y'.
327
328config MTD_CFI_FLAGADM
329	tristate "CFI Flash device mapping on FlagaDM"
330	depends on 8xx && MTD_CFI
331	help
332	  Mapping for the Flaga digital module. If you don't have one, ignore
333	  this setting.
334
335config MTD_REDWOOD
336	tristate "CFI Flash devices mapped on IBM Redwood"
337	depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
338	help
339	  This enables access routines for the flash chips on the IBM
340	  Redwood board. If you have one of these boards and would like to
341	  use the flash chips on it, say 'Y'.
342
343config MTD_SOLUTIONENGINE
344	tristate "CFI Flash device mapped on Hitachi SolutionEngine"
345	depends on SUPERH && SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS
346	help
347	  This enables access to the flash chips on the Hitachi SolutionEngine and
348	  similar boards. Say 'Y' if you are building a kernel for such a board.
349
350config MTD_ARM_INTEGRATOR
351	tristate "CFI Flash device mapped on ARM Integrator/P720T"
352	depends on ARM && MTD_CFI
353
354config MTD_CDB89712
355	tristate "Cirrus CDB89712 evaluation board mappings"
356	depends on MTD_CFI && ARCH_CDB89712
357	help
358	  This enables access to the flash or ROM chips on the CDB89712 board.
359	  If you have such a board, say 'Y'.
360
361config MTD_SA1100
362	tristate "CFI Flash device mapped on StrongARM SA11x0"
363	depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
364	help
365	  This enables access to the flash chips on most platforms based on
366	  the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
367	  If you have such a board, say 'Y'.
368
369config MTD_IPAQ
370	tristate "CFI Flash device mapped on Compaq/HP iPAQ"
371	depends on IPAQ_HANDHELD && MTD_CFI
372	help
373	  This provides a driver for the on-board flash of the iPAQ.
374
375config MTD_DC21285
376	tristate "CFI Flash device mapped on DC21285 Footbridge"
377	depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
378	help
379	  This provides a driver for the flash accessed using Intel's
380	  21285 bridge used with Intel's StrongARM processors. More info at
381	  <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
382
383config MTD_IXP4XX
384	tristate "CFI Flash device mapped on Intel IXP4xx based systems"
385	depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
386	help
387	  This enables MTD access to flash devices on platforms based
388	  on Intel's IXP4xx family of network processors such as the
389	  IXDP425 and Coyote. If you have an IXP4xx based board and
390	  would like to use the flash chips on it, say 'Y'.
391
392config MTD_IXP2000
393	tristate "CFI Flash device mapped on Intel IXP2000 based systems"
394	depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
395	help
396	  This enables MTD access to flash devices on platforms based
397	  on Intel's IXP2000 family of network processors such as the
398	  IXDP425 and Coyote. If you have an IXP2000 based board and
399	  would like to use the flash chips on it, say 'Y'.
400
401config MTD_FORTUNET
402	tristate "CFI Flash device mapped on the FortuNet board"
403	depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
404	help
405	  This enables access to the Flash on the FortuNet board.  If you
406	  have such a board, say 'Y'.
407
408config MTD_AUTCPU12
409	tristate "NV-RAM mapping AUTCPU12 board"
410	depends on ARCH_AUTCPU12
411	help
412	  This enables access to the NV-RAM on autronix autcpu12 board.
413	  If you have such a board, say 'Y'.
414
415config MTD_EDB7312
416	tristate "CFI Flash device mapped on EDB7312"
417	depends on ARCH_EDB7312 && MTD_CFI
418	help
419	  This enables access to the CFI Flash on the Cogent EDB7312 board.
420	  If you have such a board, say 'Y' here.
421
422config MTD_IMPA7
423	tristate "JEDEC Flash device mapped on impA7"
424	depends on ARM && MTD_JEDECPROBE
425	help
426	  This enables access to the NOR Flash on the impA7 board of
427	  implementa GmbH. If you have such a board, say 'Y' here.
428
429config MTD_CEIVA
430	tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
431	depends on MTD_JEDECPROBE && ARCH_CEIVA
432	help
433	  This enables access to the flash chips on the Ceiva/Polaroid
434	  PhotoMax Digital Picture Frame.
435	  If you have such a device, say 'Y'.
436
437config MTD_H720X
438	tristate "Hynix evaluation board mappings"
439	depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
440	help
441	  This enables access to the flash chips on the Hynix evaluation boards.
442	  If you have such a board, say 'Y'.
443
444config MTD_OMAP_NOR
445	tristate "TI OMAP board mappings"
446	depends on MTD_CFI && ARCH_OMAP
447	help
448	  This enables access to the NOR flash chips on TI OMAP-based
449	  boards defining flash platform devices and flash platform data.
450	  These boards include the Innovator, H2, H3, OSK, Perseus2, and
451	  more.  If you have such a board, say 'Y'.
452
453# This needs CFI or JEDEC, depending on the cards found.
454config MTD_PCI
455	tristate "PCI MTD driver"
456	depends on PCI && MTD_COMPLEX_MAPPINGS
457	help
458	  Mapping for accessing flash devices on add-in cards like the Intel XScale
459	  IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
460	  (please see the manual for the link settings).
461
462	  If you are not sure, say N.
463
464config MTD_PCMCIA
465	tristate "PCMCIA MTD driver"
466	depends on PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
467	help
468	  Map driver for accessing PCMCIA linear flash memory cards. These
469	  cards are usually around 4-16MiB in size. This does not include
470	  Compact Flash cards which are treated as IDE devices.
471
472config MTD_PCMCIA_ANONYMOUS
473	bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
474	depends on MTD_PCMCIA
475	help
476	  If this option is enabled, PCMCIA cards which do not report
477	  anything about themselves are assumed to be MTD cards.
478
479	  If unsure, say N.
480
481config MTD_BFIN_ASYNC
482	tristate "Blackfin BF533-STAMP Flash Chip Support"
483	depends on BFIN533_STAMP && MTD_CFI
484	select MTD_PARTITIONS
485	default y
486	help
487	  Map driver which allows for simultaneous utilization of
488	  ethernet and CFI parallel flash.
489
490	  If compiled as a module, it will be called bfin-async-flash.
491
492config MTD_UCLINUX
493	tristate "Generic uClinux RAM/ROM filesystem support"
494	depends on MTD_PARTITIONS && MTD_RAM && !MMU
495	help
496	  Map driver to support image based filesystems for uClinux.
497
498config MTD_WRSBC8260
499	tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
500	depends on (SBC82xx || SBC8560)
501	select MTD_PARTITIONS
502	select MTD_MAP_BANK_WIDTH_4
503	select MTD_MAP_BANK_WIDTH_1
504	select MTD_CFI_I1
505	select MTD_CFI_I4
506	help
507	  Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
508	  all three flash regions on CS0, CS1 and CS6 if they are configured
509	  correctly by the boot loader.
510
511config MTD_DMV182
512        tristate "Map driver for Dy-4 SVME/DMV-182 board."
513        depends on DMV182
514        select MTD_PARTITIONS
515	select MTD_MAP_BANK_WIDTH_32
516	select MTD_CFI_I8
517	select MTD_CFI_AMDSTD
518        help
519          Map driver for Dy-4 SVME/DMV-182 board.
520
521config MTD_SHARP_SL
522	tristate "ROM mapped on Sharp SL Series"
523	depends on ARCH_PXA
524	help
525	  This enables access to the flash chip on the Sharp SL Series of PDAs.
526
527config MTD_INTEL_VR_NOR
528	tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
529	depends on PCI
530	help
531	  Map driver for a NOR flash bank located on the Expansion Bus of the
532	  Intel Vermilion Range chipset.
533
534config MTD_PLATRAM
535	tristate "Map driver for platform device RAM (mtd-ram)"
536	select MTD_RAM
537	help
538	  Map driver for RAM areas described via the platform device
539	  system.
540
541	  This selection automatically selects the map_ram driver.
542
543endmenu
544
545