1# SPDX-License-Identifier: GPL-2.0-only 2menu "Mapping drivers for chip access" 3 depends on MTD!=n 4 depends on HAS_IOMEM 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 "Flash device in physical memory map" 14 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_RAM || 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 26config 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 37config 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 47config 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 59config MTD_PHYSMAP_BANKWIDTH 60 int "Bank width in octets" 61 depends on MTD_PHYSMAP_COMPAT 62 default "2" 63 help 64 This is the total width of the data bus of the flash devices 65 in octets. For example, if you have a data bus width of 32 66 bits, you would set the bus width octet value to 4. This is 67 used internally by the CFI drivers. 68 69config MTD_PHYSMAP_OF 70 bool "Memory device in physical memory map based on OF description" 71 depends on OF && MTD_PHYSMAP 72 help 73 This provides a 'mapping' driver which allows the NOR Flash, ROM 74 and RAM driver code to communicate with chips which are mapped 75 physically into the CPU's memory. The mapping description here is 76 taken from OF device tree. 77 78config MTD_PHYSMAP_VERSATILE 79 bool "ARM Versatile OF-based physical memory map handling" 80 depends on MTD_PHYSMAP_OF 81 depends on MFD_SYSCON 82 default y if (ARCH_INTEGRATOR || ARCH_VERSATILE || ARCH_REALVIEW) 83 help 84 This provides some extra DT physmap parsing for the ARM Versatile 85 platforms, basically to add a VPP (write protection) callback so 86 the flash can be taken out of write protection. 87 88config MTD_PHYSMAP_GEMINI 89 bool "Cortina Gemini OF-based physical memory map handling" 90 depends on MTD_PHYSMAP_OF 91 depends on MFD_SYSCON 92 select MTD_COMPLEX_MAPPINGS 93 default ARCH_GEMINI 94 help 95 This provides some extra DT physmap parsing for the Gemini 96 platforms, some detection and setting up parallel mode on the 97 external interface. 98 99config MTD_PHYSMAP_IXP4XX 100 bool "Intel IXP4xx OF-based physical memory map handling" 101 depends on MTD_PHYSMAP_OF 102 depends on ARM 103 select MTD_COMPLEX_MAPPINGS 104 select MTD_CFI_BE_BYTE_SWAP if CPU_BIG_ENDIAN 105 default ARCH_IXP4XX 106 help 107 This provides some extra DT physmap parsing for the Intel IXP4xx 108 platforms, some elaborate endianness handling in particular. 109 110config MTD_PHYSMAP_GPIO_ADDR 111 bool "GPIO-assisted Flash Chip Support" 112 depends on MTD_PHYSMAP 113 depends on GPIOLIB || COMPILE_TEST 114 depends on MTD_COMPLEX_MAPPINGS 115 help 116 Extend the physmap driver to allow flashes to be partially 117 physically addressed and assisted by GPIOs. 118 119config MTD_SUN_UFLASH 120 tristate "Sun Microsystems userflash support" 121 depends on SPARC && MTD_CFI && PCI 122 help 123 This provides a 'mapping' driver which supports the way in 124 which user-programmable flash chips are connected on various 125 Sun Microsystems boardsets. This driver will require CFI support 126 in the kernel, so if you did not enable CFI previously, do that now. 127 128config MTD_SC520CDP 129 tristate "CFI Flash device mapped on AMD SC520 CDP" 130 depends on (MELAN || COMPILE_TEST) && MTD_CFI 131 help 132 The SC520 CDP board has two banks of CFI-compliant chips and one 133 Dual-in-line JEDEC chip. This 'mapping' driver supports that 134 arrangement, implementing three MTD devices. 135 136config MTD_SBC_GXX 137 tristate "CFI Flash device mapped on Arcom SBC-GXx boards" 138 depends on X86 && MTD_CFI_INTELEXT && MTD_COMPLEX_MAPPINGS 139 help 140 This provides a driver for the on-board flash of Arcom Control 141 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX. 142 By default the flash is split into 3 partitions which are accessed 143 as separate MTD devices. This board utilizes Intel StrataFlash. 144 More info at 145 <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>. 146 147config MTD_PXA2XX 148 tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards" 149 depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT 150 help 151 This provides a driver for the NOR flash attached to a PXA2xx chip. 152 153config MTD_SCx200_DOCFLASH 154 tristate "Flash device mapped with DOCCS on NatSemi SCx200" 155 depends on SCx200 && MTD_CFI 156 help 157 Enable support for a flash chip mapped using the DOCCS signal on a 158 National Semiconductor SCx200 processor. 159 160 If you don't know what to do here, say N. 161 162 If compiled as a module, it will be called scx200_docflash. 163 164config MTD_AMD76XROM 165 tristate "BIOS flash chip on AMD76x southbridge" 166 depends on X86 && MTD_JEDECPROBE 167 help 168 Support for treating the BIOS flash chip on AMD76x motherboards 169 as an MTD device - with this you can reprogram your BIOS. 170 171 BE VERY CAREFUL. 172 173config MTD_ICHXROM 174 tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5" 175 depends on X86 && MTD_JEDECPROBE 176 help 177 Support for treating the BIOS flash chip on ICHX motherboards 178 as an MTD device - with this you can reprogram your BIOS. 179 180 BE VERY CAREFUL. 181 182config MTD_ESB2ROM 183 tristate "BIOS flash chip on Intel ESB Controller Hub 2" 184 depends on X86 && MTD_JEDECPROBE && PCI 185 help 186 Support for treating the BIOS flash chip on ESB2 motherboards 187 as an MTD device - with this you can reprogram your BIOS. 188 189 BE VERY CAREFUL. 190 191config MTD_CK804XROM 192 tristate "BIOS flash chip on Nvidia CK804" 193 depends on X86 && MTD_JEDECPROBE && PCI 194 help 195 Support for treating the BIOS flash chip on nvidia motherboards 196 as an MTD device - with this you can reprogram your BIOS. 197 198 BE VERY CAREFUL. 199 200config MTD_SCB2_FLASH 201 tristate "BIOS flash chip on Intel SCB2 boards" 202 depends on X86 && MTD_JEDECPROBE && PCI 203 help 204 Support for treating the BIOS flash chip on Intel SCB2 boards 205 as an MTD device - with this you can reprogram your BIOS. 206 207 BE VERY CAREFUL. 208 209config MTD_TSUNAMI 210 tristate "Flash chips on Tsunami TIG bus" 211 depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS 212 help 213 Support for the flash chip on Tsunami TIG bus. 214 215config MTD_NETtel 216 tristate "CFI flash device on SnapGear/SecureEdge" 217 depends on X86 && MTD_JEDECPROBE 218 help 219 Support for flash chips on NETtel/SecureEdge/SnapGear boards. 220 221config MTD_LANTIQ 222 tristate "Lantiq SoC NOR support" 223 depends on LANTIQ 224 help 225 Support for NOR flash attached to the Lantiq SoC's External Bus Unit. 226 227config MTD_L440GX 228 tristate "BIOS flash chip on Intel L440GX boards" 229 depends on X86 && MTD_JEDECPROBE 230 help 231 Support for treating the BIOS flash chip on Intel L440GX motherboards 232 as an MTD device - with this you can reprogram your BIOS. 233 234 BE VERY CAREFUL. 235 236config MTD_CFI_FLAGADM 237 tristate "CFI Flash device mapping on FlagaDM" 238 depends on PPC_8xx && MTD_CFI 239 help 240 Mapping for the Flaga digital module. If you don't have one, ignore 241 this setting. 242 243config MTD_SOLUTIONENGINE 244 tristate "CFI Flash device mapped on Hitachi SolutionEngine" 245 depends on SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS 246 help 247 This enables access to the flash chips on the Hitachi SolutionEngine and 248 similar boards. Say 'Y' if you are building a kernel for such a board. 249 250config MTD_SA1100 251 tristate "CFI Flash device mapped on StrongARM SA11x0" 252 depends on MTD_CFI && ARCH_SA1100 253 help 254 This enables access to the flash chips on most platforms based on 255 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ. 256 If you have such a board, say 'Y'. 257 258config MTD_DC21285 259 tristate "CFI Flash device mapped on DC21285 Footbridge" 260 depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS 261 help 262 This provides a driver for the flash accessed using Intel's 263 21285 bridge used with Intel's StrongARM processors. More info at 264 <https://www.intel.com/design/bridge/docs/21285_documentation.htm>. 265 266config MTD_IMPA7 267 tristate "JEDEC Flash device mapped on impA7" 268 depends on ARM && MTD_JEDECPROBE 269 help 270 This enables access to the NOR Flash on the impA7 board of 271 implementa GmbH. If you have such a board, say 'Y' here. 272 273# This needs CFI or JEDEC, depending on the cards found. 274config MTD_PCI 275 tristate "PCI MTD driver" 276 depends on PCI && MTD_COMPLEX_MAPPINGS 277 help 278 Mapping for accessing flash devices on add-in cards like the Intel XScale 279 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode 280 (please see the manual for the link settings). 281 282 If you are not sure, say N. 283 284config MTD_PCMCIA 285 tristate "PCMCIA MTD driver" 286 depends on PCMCIA && MTD_COMPLEX_MAPPINGS 287 help 288 Map driver for accessing PCMCIA linear flash memory cards. These 289 cards are usually around 4-16MiB in size. This does not include 290 Compact Flash cards which are treated as IDE devices. 291 292config MTD_PCMCIA_ANONYMOUS 293 bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards" 294 depends on MTD_PCMCIA 295 help 296 If this option is enabled, PCMCIA cards which do not report 297 anything about themselves are assumed to be MTD cards. 298 299 If unsure, say N. 300 301config MTD_UCLINUX 302 bool "Generic uClinux RAM/ROM filesystem support" 303 depends on (MTD_RAM=y || MTD_ROM=y) && (!MMU || COLDFIRE) 304 help 305 Map driver to support image based filesystems for uClinux. 306 307config MTD_PLATRAM 308 tristate "Map driver for platform device RAM (mtd-ram)" 309 select MTD_RAM 310 help 311 Map driver for RAM areas described via the platform device 312 system. 313 314 This selection automatically selects the map_ram driver. 315 316config MTD_VMU 317 tristate "Map driver for Dreamcast VMU" 318 depends on MAPLE 319 help 320 This driver enables access to the Dreamcast Visual Memory Unit (VMU). 321 322 Most Dreamcast users will want to say Y here. 323 324 To build this as a module select M here, the module will be called 325 vmu-flash. 326 327config MTD_PISMO 328 tristate "MTD discovery driver for PISMO modules" 329 depends on I2C 330 depends on ARCH_VERSATILE 331 help 332 This driver allows for discovery of PISMO modules - see 333 <http://www.pismoworld.org/>. These are small modules containing 334 up to five memory devices (eg, SRAM, flash, DOC) described by an 335 I2C EEPROM. 336 337 This driver does not create any MTD maps itself; instead it 338 creates MTD physmap and MTD SRAM platform devices. If you 339 enable this option, you should consider enabling MTD_PHYSMAP 340 and/or MTD_PLATRAM according to the devices on your module. 341 342 When built as a module, it will be called pismo.ko 343 344endmenu 345