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