drivers/mtd/maps/Kconfig

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