382 lines · plain
1# SPDX-License-Identifier: GPL-2.0-only2menu "Mapping drivers for chip access"3 depends on MTD!=n4 depends on HAS_IOMEM5 6config MTD_COMPLEX_MAPPINGS7 bool "Support non-linear mappings of flash chips"8 help9 This causes the chip drivers to allow for complicated10 paged mappings of flash chips.11 12config MTD_PHYSMAP13 tristate "Flash device in physical memory map"14 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_RAM || MTD_LPDDR15 help16 This provides a 'mapping' driver which allows the NOR Flash and17 ROM driver code to communicate with chips which are mapped18 physically into the CPU's memory. You will need to configure19 the physical address and size of the flash chips on your20 particular board as well as the bus width, either statically21 with config options or at run-time.22 23 To compile this driver as a module, choose M here: the24 module will be called physmap.25 26config MTD_PHYSMAP_COMPAT27 bool "Physmap compat support"28 depends on MTD_PHYSMAP29 default n30 help31 Setup a simple mapping via the Kconfig options. Normally the32 physmap configuration options are done via your board's33 resource file.34 35 If unsure, say N here.36 37config MTD_PHYSMAP_START38 hex "Physical start address of flash mapping"39 depends on MTD_PHYSMAP_COMPAT40 default "0x8000000"41 help42 This is the physical memory location at which the flash chips43 are mapped on your particular target board. Refer to the44 memory map which should hopefully be in the documentation for45 your board.46 47config MTD_PHYSMAP_LEN48 hex "Physical length of flash mapping"49 depends on MTD_PHYSMAP_COMPAT50 default "0"51 help52 This is the total length of the mapping of the flash chips on53 your particular board. If there is space, or aliases, in the54 physical memory map between the chips, this could be larger55 than the total amount of flash present. Refer to the memory56 map which should hopefully be in the documentation for your57 board.58 59config MTD_PHYSMAP_BANKWIDTH60 int "Bank width in octets"61 depends on MTD_PHYSMAP_COMPAT62 default "2"63 help64 This is the total width of the data bus of the flash devices65 in octets. For example, if you have a data bus width of 3266 bits, you would set the bus width octet value to 4. This is67 used internally by the CFI drivers.68 69config MTD_PHYSMAP_OF70 bool "Memory device in physical memory map based on OF description"71 depends on OF && MTD_PHYSMAP72 help73 This provides a 'mapping' driver which allows the NOR Flash, ROM74 and RAM driver code to communicate with chips which are mapped75 physically into the CPU's memory. The mapping description here is76 taken from OF device tree.77 78config MTD_PHYSMAP_BT1_ROM79 bool "Baikal-T1 Boot ROMs OF-based physical memory map handling"80 depends on MTD_PHYSMAP_OF81 depends on MIPS_BAIKAL_T1 || COMPILE_TEST82 select MTD_COMPLEX_MAPPINGS83 select MULTIPLEXER84 select MUX_MMIO85 help86 This provides some extra DT physmap parsing for the Baikal-T187 platforms, some detection and setting up ROMs-specific accessors.88 89config MTD_PHYSMAP_VERSATILE90 bool "ARM Versatile OF-based physical memory map handling"91 depends on MTD_PHYSMAP_OF92 depends on MFD_SYSCON93 default y if (ARCH_INTEGRATOR || ARCH_VERSATILE || ARCH_REALVIEW)94 help95 This provides some extra DT physmap parsing for the ARM Versatile96 platforms, basically to add a VPP (write protection) callback so97 the flash can be taken out of write protection.98 99config MTD_PHYSMAP_GEMINI100 bool "Cortina Gemini OF-based physical memory map handling"101 depends on MTD_PHYSMAP_OF102 depends on MFD_SYSCON103 select MTD_COMPLEX_MAPPINGS104 default ARCH_GEMINI105 help106 This provides some extra DT physmap parsing for the Gemini107 platforms, some detection and setting up parallel mode on the108 external interface.109 110config MTD_PHYSMAP_IXP4XX111 bool "Intel IXP4xx OF-based physical memory map handling"112 depends on MTD_PHYSMAP_OF113 depends on ARM114 select MTD_COMPLEX_MAPPINGS115 select MTD_CFI_BE_BYTE_SWAP if CPU_BIG_ENDIAN116 default ARCH_IXP4XX117 help118 This provides some extra DT physmap parsing for the Intel IXP4xx119 platforms, some elaborate endianness handling in particular.120 121config MTD_PHYSMAP_GPIO_ADDR122 bool "GPIO-assisted Flash Chip Support"123 depends on MTD_PHYSMAP124 depends on GPIOLIB || COMPILE_TEST125 depends on MTD_COMPLEX_MAPPINGS126 help127 Extend the physmap driver to allow flashes to be partially128 physically addressed and assisted by GPIOs.129 130config MTD_SUN_UFLASH131 tristate "Sun Microsystems userflash support"132 depends on SPARC && MTD_CFI && PCI133 help134 This provides a 'mapping' driver which supports the way in135 which user-programmable flash chips are connected on various136 Sun Microsystems boardsets. This driver will require CFI support137 in the kernel, so if you did not enable CFI previously, do that now.138 139config MTD_SC520CDP140 tristate "CFI Flash device mapped on AMD SC520 CDP"141 depends on (MELAN || COMPILE_TEST) && MTD_CFI142 help143 The SC520 CDP board has two banks of CFI-compliant chips and one144 Dual-in-line JEDEC chip. This 'mapping' driver supports that145 arrangement, implementing three MTD devices.146 147config MTD_NETSC520148 tristate "CFI Flash device mapped on AMD NetSc520"149 depends on (MELAN || COMPILE_TEST) && MTD_CFI150 help151 This enables access routines for the flash chips on the AMD NetSc520152 demonstration board. If you have one of these boards and would like153 to use the flash chips on it, say 'Y'.154 155config MTD_TS5500156 tristate "JEDEC Flash device mapped on Technologic Systems TS-5500"157 depends on TS5500 || COMPILE_TEST158 select MTD_JEDECPROBE159 select MTD_CFI_AMDSTD160 help161 This provides a driver for the on-board flash of the Technologic162 System's TS-5500 board. The 2MB flash is split into 3 partitions163 which are accessed as separate MTD devices.164 165 mtd0 and mtd2 are the two BIOS drives, which use the resident166 flash disk (RFD) flash translation layer.167 168 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.169 170 Note that jumper 3 ("Write Enable Drive A") must be set171 otherwise detection won't succeed.172 173config MTD_SBC_GXX174 tristate "CFI Flash device mapped on Arcom SBC-GXx boards"175 depends on X86 && MTD_CFI_INTELEXT && MTD_COMPLEX_MAPPINGS176 help177 This provides a driver for the on-board flash of Arcom Control178 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.179 By default the flash is split into 3 partitions which are accessed180 as separate MTD devices. This board utilizes Intel StrataFlash.181 More info at182 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>.183 184config MTD_PXA2XX185 tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards"186 depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT187 help188 This provides a driver for the NOR flash attached to a PXA2xx chip.189 190config MTD_SCx200_DOCFLASH191 tristate "Flash device mapped with DOCCS on NatSemi SCx200"192 depends on SCx200 && MTD_CFI193 help194 Enable support for a flash chip mapped using the DOCCS signal on a195 National Semiconductor SCx200 processor.196 197 If you don't know what to do here, say N.198 199 If compiled as a module, it will be called scx200_docflash.200 201config MTD_AMD76XROM202 tristate "BIOS flash chip on AMD76x southbridge"203 depends on X86 && MTD_JEDECPROBE204 help205 Support for treating the BIOS flash chip on AMD76x motherboards206 as an MTD device - with this you can reprogram your BIOS.207 208 BE VERY CAREFUL.209 210config MTD_ICHXROM211 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5"212 depends on X86 && MTD_JEDECPROBE213 help214 Support for treating the BIOS flash chip on ICHX motherboards215 as an MTD device - with this you can reprogram your BIOS.216 217 BE VERY CAREFUL.218 219config MTD_ESB2ROM220 tristate "BIOS flash chip on Intel ESB Controller Hub 2"221 depends on X86 && MTD_JEDECPROBE && PCI222 help223 Support for treating the BIOS flash chip on ESB2 motherboards224 as an MTD device - with this you can reprogram your BIOS.225 226 BE VERY CAREFUL.227 228config MTD_CK804XROM229 tristate "BIOS flash chip on Nvidia CK804"230 depends on X86 && MTD_JEDECPROBE && PCI231 help232 Support for treating the BIOS flash chip on nvidia motherboards233 as an MTD device - with this you can reprogram your BIOS.234 235 BE VERY CAREFUL.236 237config MTD_SCB2_FLASH238 tristate "BIOS flash chip on Intel SCB2 boards"239 depends on X86 && MTD_JEDECPROBE && PCI240 help241 Support for treating the BIOS flash chip on Intel SCB2 boards242 as an MTD device - with this you can reprogram your BIOS.243 244 BE VERY CAREFUL.245 246config MTD_TSUNAMI247 tristate "Flash chips on Tsunami TIG bus"248 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS249 help250 Support for the flash chip on Tsunami TIG bus.251 252config MTD_NETtel253 tristate "CFI flash device on SnapGear/SecureEdge"254 depends on X86 && MTD_JEDECPROBE255 help256 Support for flash chips on NETtel/SecureEdge/SnapGear boards.257 258config MTD_LANTIQ259 tristate "Lantiq SoC NOR support"260 depends on LANTIQ261 help262 Support for NOR flash attached to the Lantiq SoC's External Bus Unit.263 264config MTD_L440GX265 tristate "BIOS flash chip on Intel L440GX boards"266 depends on X86 && MTD_JEDECPROBE267 help268 Support for treating the BIOS flash chip on Intel L440GX motherboards269 as an MTD device - with this you can reprogram your BIOS.270 271 BE VERY CAREFUL.272 273config MTD_CFI_FLAGADM274 tristate "CFI Flash device mapping on FlagaDM"275 depends on PPC_8xx && MTD_CFI276 help277 Mapping for the Flaga digital module. If you don't have one, ignore278 this setting.279 280config MTD_SOLUTIONENGINE281 tristate "CFI Flash device mapped on Hitachi SolutionEngine"282 depends on SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS283 help284 This enables access to the flash chips on the Hitachi SolutionEngine and285 similar boards. Say 'Y' if you are building a kernel for such a board.286 287config MTD_SA1100288 tristate "CFI Flash device mapped on StrongARM SA11x0"289 depends on MTD_CFI && ARCH_SA1100290 help291 This enables access to the flash chips on most platforms based on292 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.293 If you have such a board, say 'Y'.294 295config MTD_DC21285296 tristate "CFI Flash device mapped on DC21285 Footbridge"297 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS298 help299 This provides a driver for the flash accessed using Intel's300 21285 bridge used with Intel's StrongARM processors. More info at301 <https://www.intel.com/design/bridge/docs/21285_documentation.htm>.302 303config MTD_IMPA7304 tristate "JEDEC Flash device mapped on impA7"305 depends on ARM && MTD_JEDECPROBE306 help307 This enables access to the NOR Flash on the impA7 board of308 implementa GmbH. If you have such a board, say 'Y' here.309 310# This needs CFI or JEDEC, depending on the cards found.311config MTD_PCI312 tristate "PCI MTD driver"313 depends on PCI && MTD_COMPLEX_MAPPINGS314 help315 Mapping for accessing flash devices on add-in cards like the Intel XScale316 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode317 (please see the manual for the link settings).318 319 If you are not sure, say N.320 321config MTD_PCMCIA322 tristate "PCMCIA MTD driver"323 depends on PCMCIA && MTD_COMPLEX_MAPPINGS324 help325 Map driver for accessing PCMCIA linear flash memory cards. These326 cards are usually around 4-16MiB in size. This does not include327 Compact Flash cards which are treated as IDE devices.328 329config MTD_PCMCIA_ANONYMOUS330 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards"331 depends on MTD_PCMCIA332 help333 If this option is enabled, PCMCIA cards which do not report334 anything about themselves are assumed to be MTD cards.335 336 If unsure, say N.337 338config MTD_UCLINUX339 bool "Generic uClinux RAM/ROM filesystem support"340 depends on (MTD_RAM=y || MTD_ROM=y) && (!MMU || COLDFIRE)341 help342 Map driver to support image based filesystems for uClinux.343 344config MTD_PLATRAM345 tristate "Map driver for platform device RAM (mtd-ram)"346 select MTD_RAM347 help348 Map driver for RAM areas described via the platform device349 system.350 351 This selection automatically selects the map_ram driver.352 353config MTD_VMU354 tristate "Map driver for Dreamcast VMU"355 depends on MAPLE356 help357 This driver enables access to the Dreamcast Visual Memory Unit (VMU).358 359 Most Dreamcast users will want to say Y here.360 361 To build this as a module select M here, the module will be called362 vmu-flash.363 364config MTD_PISMO365 tristate "MTD discovery driver for PISMO modules"366 depends on I2C367 depends on ARCH_VERSATILE368 help369 This driver allows for discovery of PISMO modules - see370 <http://www.pismoworld.org/>. These are small modules containing371 up to five memory devices (eg, SRAM, flash, DOC) described by an372 I2C EEPROM.373 374 This driver does not create any MTD maps itself; instead it375 creates MTD physmap and MTD SRAM platform devices. If you376 enable this option, you should consider enabling MTD_PHYSMAP377 and/or MTD_PLATRAM according to the devices on your module.378 379 When built as a module, it will be called pismo.ko380 381endmenu382