xref: /openbmc/linux/drivers/mtd/maps/Kconfig (revision da2014a2)
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_WALNUT
336	tristate "Flash device mapped on IBM 405GP Walnut"
337	depends on MTD_JEDECPROBE && WALNUT && !PPC_MERGE
338	help
339	  This enables access routines for the flash chips on the IBM 405GP
340	  Walnut board. If you have one of these boards and would like to
341	  use the flash chips on it, say 'Y'.
342
343config MTD_EBONY
344	tristate "Flash devices mapped on IBM 440GP Ebony"
345	depends on MTD_JEDECPROBE && EBONY && !PPC_MERGE
346	help
347	  This enables access routines for the flash chips on the IBM 440GP
348	  Ebony board. If you have one of these boards and would like to
349	  use the flash chips on it, say 'Y'.
350
351config MTD_OCOTEA
352	tristate "Flash devices mapped on IBM 440GX Ocotea"
353	depends on MTD_CFI && OCOTEA && !PPC_MERGE
354	help
355	  This enables access routines for the flash chips on the IBM 440GX
356	  Ocotea board. If you have one of these boards and would like to
357	  use the flash chips on it, say 'Y'.
358
359config MTD_REDWOOD
360	tristate "CFI Flash devices mapped on IBM Redwood"
361	depends on MTD_CFI && ( REDWOOD_4 || REDWOOD_5 || REDWOOD_6 )
362	help
363	  This enables access routines for the flash chips on the IBM
364	  Redwood board. If you have one of these boards and would like to
365	  use the flash chips on it, say 'Y'.
366
367config MTD_SOLUTIONENGINE
368	tristate "CFI Flash device mapped on Hitachi SolutionEngine"
369	depends on SUPERH && SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS
370	help
371	  This enables access to the flash chips on the Hitachi SolutionEngine and
372	  similar boards. Say 'Y' if you are building a kernel for such a board.
373
374config MTD_ARM_INTEGRATOR
375	tristate "CFI Flash device mapped on ARM Integrator/P720T"
376	depends on ARM && MTD_CFI
377
378config MTD_CDB89712
379	tristate "Cirrus CDB89712 evaluation board mappings"
380	depends on MTD_CFI && ARCH_CDB89712
381	help
382	  This enables access to the flash or ROM chips on the CDB89712 board.
383	  If you have such a board, say 'Y'.
384
385config MTD_SA1100
386	tristate "CFI Flash device mapped on StrongARM SA11x0"
387	depends on MTD_CFI && ARCH_SA1100 && MTD_PARTITIONS
388	help
389	  This enables access to the flash chips on most platforms based on
390	  the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
391	  If you have such a board, say 'Y'.
392
393config MTD_IPAQ
394	tristate "CFI Flash device mapped on Compaq/HP iPAQ"
395	depends on IPAQ_HANDHELD && MTD_CFI
396	help
397	  This provides a driver for the on-board flash of the iPAQ.
398
399config MTD_DC21285
400	tristate "CFI Flash device mapped on DC21285 Footbridge"
401	depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS
402	help
403	  This provides a driver for the flash accessed using Intel's
404	  21285 bridge used with Intel's StrongARM processors. More info at
405	  <http://www.intel.com/design/bridge/docs/21285_documentation.htm>.
406
407config MTD_IXP4XX
408	tristate "CFI Flash device mapped on Intel IXP4xx based systems"
409	depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX
410	help
411	  This enables MTD access to flash devices on platforms based
412	  on Intel's IXP4xx family of network processors such as the
413	  IXDP425 and Coyote. If you have an IXP4xx based board and
414	  would like to use the flash chips on it, say 'Y'.
415
416config MTD_IXP2000
417	tristate "CFI Flash device mapped on Intel IXP2000 based systems"
418	depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP2000
419	help
420	  This enables MTD access to flash devices on platforms based
421	  on Intel's IXP2000 family of network processors such as the
422	  IXDP425 and Coyote. If you have an IXP2000 based board and
423	  would like to use the flash chips on it, say 'Y'.
424
425config MTD_FORTUNET
426	tristate "CFI Flash device mapped on the FortuNet board"
427	depends on MTD_CFI && MTD_PARTITIONS && SA1100_FORTUNET
428	help
429	  This enables access to the Flash on the FortuNet board.  If you
430	  have such a board, say 'Y'.
431
432config MTD_AUTCPU12
433	tristate "NV-RAM mapping AUTCPU12 board"
434	depends on ARCH_AUTCPU12
435	help
436	  This enables access to the NV-RAM on autronix autcpu12 board.
437	  If you have such a board, say 'Y'.
438
439config MTD_EDB7312
440	tristate "CFI Flash device mapped on EDB7312"
441	depends on ARCH_EDB7312 && MTD_CFI
442	help
443	  This enables access to the CFI Flash on the Cogent EDB7312 board.
444	  If you have such a board, say 'Y' here.
445
446config MTD_IMPA7
447	tristate "JEDEC Flash device mapped on impA7"
448	depends on ARM && MTD_JEDECPROBE
449	help
450	  This enables access to the NOR Flash on the impA7 board of
451	  implementa GmbH. If you have such a board, say 'Y' here.
452
453config MTD_CEIVA
454	tristate "JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame"
455	depends on MTD_JEDECPROBE && ARCH_CEIVA
456	help
457	  This enables access to the flash chips on the Ceiva/Polaroid
458	  PhotoMax Digital Picture Frame.
459	  If you have such a device, say 'Y'.
460
461config MTD_NOR_TOTO
462	tristate "NOR Flash device on TOTO board"
463	depends on ARCH_OMAP && OMAP_TOTO
464	help
465	  This enables access to the NOR flash on the Texas Instruments
466	  TOTO board.
467
468config MTD_H720X
469	tristate "Hynix evaluation board mappings"
470	depends on MTD_CFI && ( ARCH_H7201 || ARCH_H7202 )
471	help
472	  This enables access to the flash chips on the Hynix evaluation boards.
473	  If you have such a board, say 'Y'.
474
475config MTD_OMAP_NOR
476	tristate "TI OMAP board mappings"
477	depends on MTD_CFI && ARCH_OMAP
478	help
479	  This enables access to the NOR flash chips on TI OMAP-based
480	  boards defining flash platform devices and flash platform data.
481	  These boards include the Innovator, H2, H3, OSK, Perseus2, and
482	  more.  If you have such a board, say 'Y'.
483
484# This needs CFI or JEDEC, depending on the cards found.
485config MTD_PCI
486	tristate "PCI MTD driver"
487	depends on PCI && MTD_COMPLEX_MAPPINGS
488	help
489	  Mapping for accessing flash devices on add-in cards like the Intel XScale
490	  IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
491	  (please see the manual for the link settings).
492
493	  If you are not sure, say N.
494
495config MTD_PCMCIA
496	tristate "PCMCIA MTD driver"
497	depends on PCMCIA && MTD_COMPLEX_MAPPINGS && BROKEN
498	help
499	  Map driver for accessing PCMCIA linear flash memory cards. These
500	  cards are usually around 4-16MiB in size. This does not include
501	  Compact Flash cards which are treated as IDE devices.
502
503config MTD_PCMCIA_ANONYMOUS
504	bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"
505	depends on MTD_PCMCIA
506	help
507	  If this option is enabled, PCMCIA cards which do not report
508	  anything about themselves are assumed to be MTD cards.
509
510	  If unsure, say N.
511
512config MTD_BFIN_ASYNC
513	tristate "Blackfin BF533-STAMP Flash Chip Support"
514	depends on BFIN533_STAMP && MTD_CFI
515	select MTD_PARTITIONS
516	default y
517	help
518	  Map driver which allows for simultaneous utilization of
519	  ethernet and CFI parallel flash.
520
521	  If compiled as a module, it will be called bfin-async-flash.
522
523config MTD_UCLINUX
524	tristate "Generic uClinux RAM/ROM filesystem support"
525	depends on MTD_PARTITIONS && !MMU
526	help
527	  Map driver to support image based filesystems for uClinux.
528
529config MTD_WRSBC8260
530	tristate "Map driver for WindRiver PowerQUICC II MPC82xx board"
531	depends on (SBC82xx || SBC8560)
532	select MTD_PARTITIONS
533	select MTD_MAP_BANK_WIDTH_4
534	select MTD_MAP_BANK_WIDTH_1
535	select MTD_CFI_I1
536	select MTD_CFI_I4
537	help
538	  Map driver for WindRiver PowerQUICC II MPC82xx board. Drives
539	  all three flash regions on CS0, CS1 and CS6 if they are configured
540	  correctly by the boot loader.
541
542config MTD_DMV182
543        tristate "Map driver for Dy-4 SVME/DMV-182 board."
544        depends on DMV182
545        select MTD_PARTITIONS
546	select MTD_MAP_BANK_WIDTH_32
547	select MTD_CFI_I8
548	select MTD_CFI_AMDSTD
549        help
550          Map driver for Dy-4 SVME/DMV-182 board.
551
552config MTD_SHARP_SL
553	tristate "ROM mapped on Sharp SL Series"
554	depends on ARCH_PXA
555	help
556	  This enables access to the flash chip on the Sharp SL Series of PDAs.
557
558config MTD_INTEL_VR_NOR
559	tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0"
560	depends on PCI
561	help
562	  Map driver for a NOR flash bank located on the Expansion Bus of the
563	  Intel Vermilion Range chipset.
564
565config MTD_PLATRAM
566	tristate "Map driver for platform device RAM (mtd-ram)"
567	select MTD_RAM
568	help
569	  Map driver for RAM areas described via the platform device
570	  system.
571
572	  This selection automatically selects the map_ram driver.
573
574endmenu
575
576