Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | menu "Mapping drivers for chip access" |
| 2 | depends on MTD!=n |
Richard Weinberger | 9310da0 | 2012-02-07 01:22:50 +0100 | [diff] [blame] | 3 | depends on HAS_IOMEM |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 4 | |
| 5 | config MTD_COMPLEX_MAPPINGS |
| 6 | bool "Support non-linear mappings of flash chips" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 7 | help |
| 8 | This causes the chip drivers to allow for complicated |
| 9 | paged mappings of flash chips. |
| 10 | |
| 11 | config MTD_PHYSMAP |
Alexey Korolev | d814083 | 2008-12-16 18:22:39 +0000 | [diff] [blame] | 12 | tristate "Flash device in physical memory map" |
| 13 | depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_LPDDR |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 14 | help |
Takashi YOSHII | 79b9cd5 | 2006-08-15 07:26:32 -0500 | [diff] [blame] | 15 | This provides a 'mapping' driver which allows the NOR Flash and |
| 16 | ROM driver code to communicate with chips which are mapped |
| 17 | physically into the CPU's memory. You will need to configure |
| 18 | the physical address and size of the flash chips on your |
| 19 | particular board as well as the bus width, either statically |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 20 | with config options or at run-time. |
| 21 | |
Mike Frysinger | 41bdf96 | 2008-04-18 13:44:10 -0700 | [diff] [blame] | 22 | To compile this driver as a module, choose M here: the |
| 23 | module will be called physmap. |
| 24 | |
Mike Frysinger | dcb3e13 | 2008-12-01 14:23:40 -0800 | [diff] [blame] | 25 | config MTD_PHYSMAP_COMPAT |
| 26 | bool "Physmap compat support" |
| 27 | depends on MTD_PHYSMAP |
| 28 | default n |
| 29 | help |
| 30 | Setup a simple mapping via the Kconfig options. Normally the |
| 31 | physmap configuration options are done via your board's |
| 32 | resource file. |
| 33 | |
| 34 | If unsure, say N here. |
| 35 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 36 | config MTD_PHYSMAP_START |
| 37 | hex "Physical start address of flash mapping" |
Mike Frysinger | dcb3e13 | 2008-12-01 14:23:40 -0800 | [diff] [blame] | 38 | depends on MTD_PHYSMAP_COMPAT |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 39 | default "0x8000000" |
| 40 | help |
| 41 | This is the physical memory location at which the flash chips |
| 42 | are mapped on your particular target board. Refer to the |
| 43 | memory map which should hopefully be in the documentation for |
| 44 | your board. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 45 | |
| 46 | config MTD_PHYSMAP_LEN |
| 47 | hex "Physical length of flash mapping" |
Mike Frysinger | dcb3e13 | 2008-12-01 14:23:40 -0800 | [diff] [blame] | 48 | depends on MTD_PHYSMAP_COMPAT |
Lennert Buytenhek | 73566ed | 2006-05-07 17:16:36 +0100 | [diff] [blame] | 49 | default "0" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 50 | help |
| 51 | This is the total length of the mapping of the flash chips on |
| 52 | your particular board. If there is space, or aliases, in the |
| 53 | physical memory map between the chips, this could be larger |
| 54 | than the total amount of flash present. Refer to the memory |
| 55 | map which should hopefully be in the documentation for your |
| 56 | board. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 57 | |
| 58 | config MTD_PHYSMAP_BANKWIDTH |
| 59 | int "Bank width in octets" |
Mike Frysinger | dcb3e13 | 2008-12-01 14:23:40 -0800 | [diff] [blame] | 60 | depends on MTD_PHYSMAP_COMPAT |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 61 | default "2" |
| 62 | help |
| 63 | This is the total width of the data bus of the flash devices |
| 64 | in octets. For example, if you have a data bus width of 32 |
Matt LaPlante | 01dd2fb | 2007-10-20 01:34:40 +0200 | [diff] [blame] | 65 | bits, you would set the bus width octet value to 4. This is |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 66 | used internally by the CFI drivers. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 67 | |
Vitaly Wool | a2c2fe4 | 2006-12-06 13:17:49 +0300 | [diff] [blame] | 68 | config MTD_PHYSMAP_OF |
Philippe De Muyter | 670b46a | 2014-03-06 00:00:00 +0100 | [diff] [blame] | 69 | tristate "Memory device in physical memory map based on OF description" |
| 70 | depends on OF && (MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_RAM) |
Vitaly Wool | a2c2fe4 | 2006-12-06 13:17:49 +0300 | [diff] [blame] | 71 | help |
Philippe De Muyter | 670b46a | 2014-03-06 00:00:00 +0100 | [diff] [blame] | 72 | This provides a 'mapping' driver which allows the NOR Flash, ROM |
| 73 | and RAM driver code to communicate with chips which are mapped |
Vitaly Wool | a2c2fe4 | 2006-12-06 13:17:49 +0300 | [diff] [blame] | 74 | physically into the CPU's memory. The mapping description here is |
| 75 | taken from OF device tree. |
| 76 | |
Linus Walleij | b0afd44 | 2016-01-26 11:58:07 +0100 | [diff] [blame] | 77 | config MTD_PHYSMAP_OF_VERSATILE |
| 78 | bool "Support ARM Versatile physmap OF" |
| 79 | depends on MTD_PHYSMAP_OF |
| 80 | depends on MFD_SYSCON |
| 81 | default y if (ARCH_INTEGRATOR || ARCH_VERSATILE || REALVIEW_DT) |
| 82 | help |
| 83 | This provides some extra DT physmap parsing for the ARM Versatile |
| 84 | platforms, basically to add a VPP (write protection) callback so |
| 85 | the flash can be taken out of write protection. |
| 86 | |
Marc St-Jean | 68aa0fa | 2007-03-26 21:45:41 -0800 | [diff] [blame] | 87 | config MTD_PMC_MSP_EVM |
| 88 | tristate "CFI Flash device mapped on PMC-Sierra MSP" |
| 89 | depends on PMC_MSP && MTD_CFI |
Marc St-Jean | 68aa0fa | 2007-03-26 21:45:41 -0800 | [diff] [blame] | 90 | help |
Matt LaPlante | 01dd2fb | 2007-10-20 01:34:40 +0200 | [diff] [blame] | 91 | This provides a 'mapping' driver which supports the way |
| 92 | in which user-programmable flash chips are connected on the |
| 93 | PMC-Sierra MSP eval/demo boards. |
Marc St-Jean | 68aa0fa | 2007-03-26 21:45:41 -0800 | [diff] [blame] | 94 | |
| 95 | choice |
Matt LaPlante | 01dd2fb | 2007-10-20 01:34:40 +0200 | [diff] [blame] | 96 | prompt "Maximum mappable memory available for flash IO" |
Marc St-Jean | 68aa0fa | 2007-03-26 21:45:41 -0800 | [diff] [blame] | 97 | depends on MTD_PMC_MSP_EVM |
| 98 | default MSP_FLASH_MAP_LIMIT_32M |
| 99 | |
| 100 | config MSP_FLASH_MAP_LIMIT_32M |
| 101 | bool "32M" |
| 102 | |
| 103 | endchoice |
| 104 | |
| 105 | config MSP_FLASH_MAP_LIMIT |
| 106 | hex |
| 107 | default "0x02000000" |
| 108 | depends on MSP_FLASH_MAP_LIMIT_32M |
| 109 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 110 | config MTD_SUN_UFLASH |
| 111 | tristate "Sun Microsystems userflash support" |
Al Viro | e0e5de0 | 2007-07-26 17:33:09 +0100 | [diff] [blame] | 112 | depends on SPARC && MTD_CFI && PCI |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 113 | help |
Thomas Gleixner | 69f34c9 | 2005-11-07 11:15:40 +0000 | [diff] [blame] | 114 | This provides a 'mapping' driver which supports the way in |
| 115 | which user-programmable flash chips are connected on various |
| 116 | Sun Microsystems boardsets. This driver will require CFI support |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 117 | in the kernel, so if you did not enable CFI previously, do that now. |
| 118 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 119 | config MTD_SC520CDP |
| 120 | tristate "CFI Flash device mapped on AMD SC520 CDP" |
Jean Delvare | 3579ad4 | 2014-03-14 18:14:20 +0100 | [diff] [blame] | 121 | depends on (MELAN || COMPILE_TEST) && MTD_CFI |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 122 | help |
| 123 | The SC520 CDP board has two banks of CFI-compliant chips and one |
| 124 | Dual-in-line JEDEC chip. This 'mapping' driver supports that |
| 125 | arrangement, implementing three MTD devices. |
| 126 | |
| 127 | config MTD_NETSC520 |
| 128 | tristate "CFI Flash device mapped on AMD NetSc520" |
Jean Delvare | 3579ad4 | 2014-03-14 18:14:20 +0100 | [diff] [blame] | 129 | depends on (MELAN || COMPILE_TEST) && MTD_CFI |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 130 | help |
| 131 | This enables access routines for the flash chips on the AMD NetSc520 |
Thomas Gleixner | 69f34c9 | 2005-11-07 11:15:40 +0000 | [diff] [blame] | 132 | demonstration board. If you have one of these boards and would like |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 133 | to use the flash chips on it, say 'Y'. |
| 134 | |
| 135 | config MTD_TS5500 |
| 136 | tristate "JEDEC Flash device mapped on Technologic Systems TS-5500" |
Jean Delvare | f4f6a0b | 2014-02-23 10:32:01 +0100 | [diff] [blame] | 137 | depends on TS5500 || COMPILE_TEST |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 138 | select MTD_JEDECPROBE |
| 139 | select MTD_CFI_AMDSTD |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 140 | help |
| 141 | This provides a driver for the on-board flash of the Technologic |
Sean Young | e27a996 | 2005-06-16 09:49:33 +0100 | [diff] [blame] | 142 | System's TS-5500 board. The 2MB flash is split into 3 partitions |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 143 | which are accessed as separate MTD devices. |
| 144 | |
Sean Young | e27a996 | 2005-06-16 09:49:33 +0100 | [diff] [blame] | 145 | mtd0 and mtd2 are the two BIOS drives, which use the resident |
| 146 | flash disk (RFD) flash translation layer. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 147 | |
| 148 | mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL. |
| 149 | |
| 150 | Note that jumper 3 ("Write Enable Drive A") must be set |
Egry Gábor | 4992a9e | 2006-05-12 17:35:02 +0100 | [diff] [blame] | 151 | otherwise detection won't succeed. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 152 | |
| 153 | config MTD_SBC_GXX |
| 154 | tristate "CFI Flash device mapped on Arcom SBC-GXx boards" |
Jamie Iles | 6a8a98b | 2011-05-23 10:23:43 +0100 | [diff] [blame] | 155 | depends on X86 && MTD_CFI_INTELEXT && MTD_COMPLEX_MAPPINGS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 156 | help |
| 157 | This provides a driver for the on-board flash of Arcom Control |
| 158 | Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX. |
| 159 | By default the flash is split into 3 partitions which are accessed |
| 160 | as separate MTD devices. This board utilizes Intel StrataFlash. |
| 161 | More info at |
| 162 | <http://www.arcomcontrols.com/products/icp/pc104/processors/SBC_GX1.htm>. |
| 163 | |
Todd Poynor | e644f7d | 2005-11-07 21:47:48 +0000 | [diff] [blame] | 164 | config MTD_PXA2XX |
| 165 | tristate "CFI Flash device mapped on Intel XScale PXA2xx based boards" |
| 166 | depends on (PXA25x || PXA27x) && MTD_CFI_INTELEXT |
Nico Pitre | cbec19a | 2005-07-01 23:55:24 +0100 | [diff] [blame] | 167 | help |
Todd Poynor | e644f7d | 2005-11-07 21:47:48 +0000 | [diff] [blame] | 168 | This provides a driver for the NOR flash attached to a PXA2xx chip. |
Nico Pitre | cbec19a | 2005-07-01 23:55:24 +0100 | [diff] [blame] | 169 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 170 | config MTD_SCx200_DOCFLASH |
| 171 | tristate "Flash device mapped with DOCCS on NatSemi SCx200" |
Jamie Iles | f6c11c1 | 2011-05-23 10:23:10 +0100 | [diff] [blame] | 172 | depends on SCx200 && MTD_CFI |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 173 | help |
| 174 | Enable support for a flash chip mapped using the DOCCS signal on a |
| 175 | National Semiconductor SCx200 processor. |
| 176 | |
| 177 | If you don't know what to do here, say N. |
| 178 | |
| 179 | If compiled as a module, it will be called scx200_docflash. |
| 180 | |
| 181 | config MTD_AMD76XROM |
| 182 | tristate "BIOS flash chip on AMD76x southbridge" |
| 183 | depends on X86 && MTD_JEDECPROBE |
| 184 | help |
| 185 | Support for treating the BIOS flash chip on AMD76x motherboards |
| 186 | as an MTD device - with this you can reprogram your BIOS. |
| 187 | |
| 188 | BE VERY CAREFUL. |
| 189 | |
| 190 | config MTD_ICHXROM |
| 191 | tristate "BIOS flash chip on Intel Controller Hub 2/3/4/5" |
| 192 | depends on X86 && MTD_JEDECPROBE |
| 193 | help |
| 194 | Support for treating the BIOS flash chip on ICHX motherboards |
| 195 | as an MTD device - with this you can reprogram your BIOS. |
| 196 | |
| 197 | BE VERY CAREFUL. |
| 198 | |
Lew Glendenning | 2917577 | 2006-10-20 14:41:04 -0700 | [diff] [blame] | 199 | config MTD_ESB2ROM |
| 200 | tristate "BIOS flash chip on Intel ESB Controller Hub 2" |
Randy Dunlap | dffbc42 | 2006-12-04 15:03:00 -0800 | [diff] [blame] | 201 | depends on X86 && MTD_JEDECPROBE && PCI |
Lew Glendenning | 2917577 | 2006-10-20 14:41:04 -0700 | [diff] [blame] | 202 | help |
| 203 | Support for treating the BIOS flash chip on ESB2 motherboards |
| 204 | as an MTD device - with this you can reprogram your BIOS. |
| 205 | |
| 206 | BE VERY CAREFUL. |
| 207 | |
Dave Olsen | 90afffc | 2006-11-06 16:33:57 -0700 | [diff] [blame] | 208 | config MTD_CK804XROM |
| 209 | tristate "BIOS flash chip on Nvidia CK804" |
akpm@osdl.org | 862c93b | 2007-01-25 15:15:17 -0800 | [diff] [blame] | 210 | depends on X86 && MTD_JEDECPROBE && PCI |
Dave Olsen | 90afffc | 2006-11-06 16:33:57 -0700 | [diff] [blame] | 211 | help |
| 212 | Support for treating the BIOS flash chip on nvidia motherboards |
| 213 | as an MTD device - with this you can reprogram your BIOS. |
| 214 | |
| 215 | BE VERY CAREFUL. |
| 216 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 217 | config MTD_SCB2_FLASH |
| 218 | tristate "BIOS flash chip on Intel SCB2 boards" |
Randy Dunlap | 47d0505 | 2012-04-16 12:50:37 -0700 | [diff] [blame] | 219 | depends on X86 && MTD_JEDECPROBE && PCI |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 220 | help |
| 221 | Support for treating the BIOS flash chip on Intel SCB2 boards |
| 222 | as an MTD device - with this you can reprogram your BIOS. |
| 223 | |
| 224 | BE VERY CAREFUL. |
| 225 | |
| 226 | config MTD_TSUNAMI |
| 227 | tristate "Flash chips on Tsunami TIG bus" |
| 228 | depends on ALPHA_TSUNAMI && MTD_COMPLEX_MAPPINGS |
| 229 | help |
| 230 | Support for the flash chip on Tsunami TIG bus. |
| 231 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 232 | config MTD_NETtel |
| 233 | tristate "CFI flash device on SnapGear/SecureEdge" |
Jamie Iles | 6a8a98b | 2011-05-23 10:23:43 +0100 | [diff] [blame] | 234 | depends on X86 && MTD_JEDECPROBE |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 235 | help |
| 236 | Support for flash chips on NETtel/SecureEdge/SnapGear boards. |
| 237 | |
John Crispin | 3c54473 | 2011-04-12 18:10:01 +0200 | [diff] [blame] | 238 | config MTD_LANTIQ |
| 239 | tristate "Lantiq SoC NOR support" |
| 240 | depends on LANTIQ |
John Crispin | 3c54473 | 2011-04-12 18:10:01 +0200 | [diff] [blame] | 241 | help |
| 242 | Support for NOR flash attached to the Lantiq SoC's External Bus Unit. |
| 243 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 244 | config MTD_L440GX |
| 245 | tristate "BIOS flash chip on Intel L440GX boards" |
| 246 | depends on X86 && MTD_JEDECPROBE |
| 247 | help |
| 248 | Support for treating the BIOS flash chip on Intel L440GX motherboards |
| 249 | as an MTD device - with this you can reprogram your BIOS. |
| 250 | |
| 251 | BE VERY CAREFUL. |
| 252 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 253 | config MTD_CFI_FLAGADM |
| 254 | tristate "CFI Flash device mapping on FlagaDM" |
Christophe Leroy | 318157a | 2015-03-12 16:24:04 +0100 | [diff] [blame] | 255 | depends on PPC_8xx && MTD_CFI |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 256 | help |
| 257 | Mapping for the Flaga digital module. If you don't have one, ignore |
| 258 | this setting. |
| 259 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 260 | config MTD_SOLUTIONENGINE |
| 261 | tristate "CFI Flash device mapped on Hitachi SolutionEngine" |
Brian Norris | 7a6f439 | 2014-07-21 19:07:56 -0700 | [diff] [blame] | 262 | depends on SOLUTION_ENGINE && MTD_CFI && MTD_REDBOOT_PARTS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 263 | help |
| 264 | This enables access to the flash chips on the Hitachi SolutionEngine and |
| 265 | similar boards. Say 'Y' if you are building a kernel for such a board. |
| 266 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 267 | config MTD_SA1100 |
| 268 | tristate "CFI Flash device mapped on StrongARM SA11x0" |
Jamie Iles | 2fe2e24 | 2011-05-23 10:23:09 +0100 | [diff] [blame] | 269 | depends on MTD_CFI && ARCH_SA1100 |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 270 | help |
| 271 | This enables access to the flash chips on most platforms based on |
| 272 | the SA1100 and SA1110, including the Assabet and the Compaq iPAQ. |
| 273 | If you have such a board, say 'Y'. |
| 274 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 275 | config MTD_DC21285 |
| 276 | tristate "CFI Flash device mapped on DC21285 Footbridge" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 277 | depends on MTD_CFI && ARCH_FOOTBRIDGE && MTD_COMPLEX_MAPPINGS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 278 | help |
| 279 | This provides a driver for the flash accessed using Intel's |
| 280 | 21285 bridge used with Intel's StrongARM processors. More info at |
| 281 | <http://www.intel.com/design/bridge/docs/21285_documentation.htm>. |
| 282 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 283 | config MTD_IXP4XX |
| 284 | tristate "CFI Flash device mapped on Intel IXP4xx based systems" |
Sean Young | 01ac742 | 2005-06-29 09:46:19 +0000 | [diff] [blame] | 285 | depends on MTD_CFI && MTD_COMPLEX_MAPPINGS && ARCH_IXP4XX |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 286 | help |
Thomas Gleixner | 69f34c9 | 2005-11-07 11:15:40 +0000 | [diff] [blame] | 287 | This enables MTD access to flash devices on platforms based |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 288 | on Intel's IXP4xx family of network processors such as the |
| 289 | IXDP425 and Coyote. If you have an IXP4xx based board and |
| 290 | would like to use the flash chips on it, say 'Y'. |
| 291 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 292 | config MTD_IMPA7 |
| 293 | tristate "JEDEC Flash device mapped on impA7" |
| 294 | depends on ARM && MTD_JEDECPROBE |
| 295 | help |
| 296 | This enables access to the NOR Flash on the impA7 board of |
| 297 | implementa GmbH. If you have such a board, say 'Y' here. |
| 298 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 299 | # This needs CFI or JEDEC, depending on the cards found. |
| 300 | config MTD_PCI |
| 301 | tristate "PCI MTD driver" |
Jan Engelhardt | ec98c68 | 2007-04-19 16:21:41 -0500 | [diff] [blame] | 302 | depends on PCI && MTD_COMPLEX_MAPPINGS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 303 | help |
| 304 | Mapping for accessing flash devices on add-in cards like the Intel XScale |
| 305 | IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode |
| 306 | (please see the manual for the link settings). |
| 307 | |
| 308 | If you are not sure, say N. |
| 309 | |
| 310 | config MTD_PCMCIA |
| 311 | tristate "PCMCIA MTD driver" |
Alexander Kurz | f6763c98 | 2010-05-13 11:59:59 +0200 | [diff] [blame] | 312 | depends on PCMCIA && MTD_COMPLEX_MAPPINGS |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 313 | help |
| 314 | Map driver for accessing PCMCIA linear flash memory cards. These |
| 315 | cards are usually around 4-16MiB in size. This does not include |
| 316 | Compact Flash cards which are treated as IDE devices. |
| 317 | |
Dominik Brodowski | 11d28a3 | 2005-06-27 16:28:32 -0700 | [diff] [blame] | 318 | config MTD_PCMCIA_ANONYMOUS |
| 319 | bool "Use PCMCIA MTD drivers for anonymous PCMCIA cards" |
| 320 | depends on MTD_PCMCIA |
Dominik Brodowski | 11d28a3 | 2005-06-27 16:28:32 -0700 | [diff] [blame] | 321 | help |
| 322 | If this option is enabled, PCMCIA cards which do not report |
| 323 | anything about themselves are assumed to be MTD cards. |
| 324 | |
| 325 | If unsure, say N. |
| 326 | |
Mike Frysinger | 2e3c22f | 2008-05-19 18:32:24 +0800 | [diff] [blame] | 327 | config MTD_BFIN_ASYNC |
| 328 | tristate "Blackfin BF533-STAMP Flash Chip Support" |
Mike Frysinger | ab00d68 | 2009-02-11 13:12:19 -0800 | [diff] [blame] | 329 | depends on BFIN533_STAMP && MTD_CFI && MTD_COMPLEX_MAPPINGS |
Mike Frysinger | 2e3c22f | 2008-05-19 18:32:24 +0800 | [diff] [blame] | 330 | default y |
| 331 | help |
| 332 | Map driver which allows for simultaneous utilization of |
| 333 | ethernet and CFI parallel flash. |
| 334 | |
| 335 | If compiled as a module, it will be called bfin-async-flash. |
| 336 | |
Mike Frysinger | d79c326 | 2009-05-20 12:04:09 -0400 | [diff] [blame] | 337 | config MTD_GPIO_ADDR |
| 338 | tristate "GPIO-assisted Flash Chip Support" |
Geert Uytterhoeven | f650ce2 | 2015-05-05 18:32:29 +0200 | [diff] [blame] | 339 | depends on GPIOLIB || COMPILE_TEST |
Mike Frysinger | d79c326 | 2009-05-20 12:04:09 -0400 | [diff] [blame] | 340 | depends on MTD_COMPLEX_MAPPINGS |
Mike Frysinger | d79c326 | 2009-05-20 12:04:09 -0400 | [diff] [blame] | 341 | help |
| 342 | Map driver which allows flashes to be partially physically addressed |
| 343 | and assisted by GPIOs. |
| 344 | |
| 345 | If compiled as a module, it will be called gpio-addr-flash. |
| 346 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 347 | config MTD_UCLINUX |
Mike Frysinger | 6ae392c | 2009-05-26 19:33:18 -0400 | [diff] [blame] | 348 | bool "Generic uClinux RAM/ROM filesystem support" |
Uwe Kleine-König | 81f53ff | 2013-01-16 15:36:55 +0100 | [diff] [blame] | 349 | depends on (MTD_RAM=y || MTD_ROM=y) && (!MMU || COLDFIRE) |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 350 | help |
| 351 | Map driver to support image based filesystems for uClinux. |
| 352 | |
David Woodhouse | 0bac511 | 2007-09-23 18:51:25 +0100 | [diff] [blame] | 353 | config MTD_INTEL_VR_NOR |
| 354 | tristate "NOR flash on Intel Vermilion Range Expansion Bus CS0" |
| 355 | depends on PCI |
| 356 | help |
| 357 | Map driver for a NOR flash bank located on the Expansion Bus of the |
| 358 | Intel Vermilion Range chipset. |
| 359 | |
Atsushi Nemoto | 610f75e | 2009-03-04 12:01:34 -0800 | [diff] [blame] | 360 | config MTD_RBTX4939 |
| 361 | tristate "Map driver for RBTX4939 board" |
| 362 | depends on TOSHIBA_RBTX4939 && MTD_CFI && MTD_COMPLEX_MAPPINGS |
| 363 | help |
| 364 | Map driver for NOR flash chips on RBTX4939 board. |
| 365 | |
Ben Dooks | 99f2a8aea | 2005-01-24 00:37:04 +0000 | [diff] [blame] | 366 | config MTD_PLATRAM |
Thomas Gleixner | 3c45e00a | 2005-03-18 02:07:24 +0000 | [diff] [blame] | 367 | tristate "Map driver for platform device RAM (mtd-ram)" |
Ben Dooks | 99f2a8aea | 2005-01-24 00:37:04 +0000 | [diff] [blame] | 368 | select MTD_RAM |
| 369 | help |
| 370 | Map driver for RAM areas described via the platform device |
| 371 | system. |
| 372 | |
| 373 | This selection automatically selects the map_ram driver. |
| 374 | |
Adrian McMenamin | 47a7268 | 2009-03-04 00:31:04 +0000 | [diff] [blame] | 375 | config MTD_VMU |
| 376 | tristate "Map driver for Dreamcast VMU" |
| 377 | depends on MAPLE |
| 378 | help |
| 379 | This driver enables access to the Dreamcast Visual Memory Unit (VMU). |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 380 | |
Adrian McMenamin | 47a7268 | 2009-03-04 00:31:04 +0000 | [diff] [blame] | 381 | Most Dreamcast users will want to say Y here. |
| 382 | |
| 383 | To build this as a module select M here, the module will be called |
| 384 | vmu-flash. |
| 385 | |
Russell King - ARM Linux | f6a8c60 | 2009-11-29 15:23:51 +0000 | [diff] [blame] | 386 | config MTD_PISMO |
| 387 | tristate "MTD discovery driver for PISMO modules" |
| 388 | depends on I2C |
| 389 | depends on ARCH_VERSATILE |
| 390 | help |
| 391 | This driver allows for discovery of PISMO modules - see |
| 392 | <http://www.pismoworld.org/>. These are small modules containing |
| 393 | up to five memory devices (eg, SRAM, flash, DOC) described by an |
| 394 | I2C EEPROM. |
| 395 | |
| 396 | This driver does not create any MTD maps itself; instead it |
| 397 | creates MTD physmap and MTD SRAM platform devices. If you |
| 398 | enable this option, you should consider enabling MTD_PHYSMAP |
| 399 | and/or MTD_PLATRAM according to the devices on your module. |
| 400 | |
| 401 | When built as a module, it will be called pismo.ko |
| 402 | |
David Griego | dcfb81d | 2010-11-30 15:32:05 +0530 | [diff] [blame] | 403 | config MTD_LATCH_ADDR |
| 404 | tristate "Latch-assisted Flash Chip Support" |
| 405 | depends on MTD_COMPLEX_MAPPINGS |
| 406 | help |
| 407 | Map driver which allows flashes to be partially physically addressed |
| 408 | and have the upper address lines set by a board specific code. |
| 409 | |
| 410 | If compiled as a module, it will be called latch-addr-flash. |
| 411 | |
Adrian McMenamin | 47a7268 | 2009-03-04 00:31:04 +0000 | [diff] [blame] | 412 | endmenu |