drivers/mtd/maps/Kconfig

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