1# SPDX-License-Identifier: GPL-2.0-only 2menu "Self-contained MTD device drivers" 3 depends on MTD!=n 4 depends on HAS_IOMEM 5 6config MTD_PMC551 7 tristate "Ramix PMC551 PCI Mezzanine RAM card support" 8 depends on PCI 9 help 10 This provides a MTD device driver for the Ramix PMC551 RAM PCI card 11 from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>. 12 These devices come in memory configurations from 32M - 1G. If you 13 have one, you probably want to enable this. 14 15 If this driver is compiled as a module you get the ability to select 16 the size of the aperture window pointing into the devices memory. 17 What this means is that if you have a 1G card, normally the kernel 18 will use a 1G memory map as its view of the device. As a module, 19 you can select a 1M window into the memory and the driver will 20 "slide" the window around the PMC551's memory. This was 21 particularly useful on the 2.2 kernels on PPC architectures as there 22 was limited kernel space to deal with. 23 24config MTD_PMC551_BUGFIX 25 bool "PMC551 256M DRAM Bugfix" 26 depends on MTD_PMC551 27 help 28 Some of Ramix's PMC551 boards with 256M configurations have invalid 29 column and row mux values. This option will fix them, but will 30 break other memory configurations. If unsure say N. 31 32config MTD_PMC551_DEBUG 33 bool "PMC551 Debugging" 34 depends on MTD_PMC551 35 help 36 This option makes the PMC551 more verbose during its operation and 37 is only really useful if you are developing on this driver or 38 suspect a possible hardware or driver bug. If unsure say N. 39 40config MTD_MS02NV 41 tristate "DEC MS02-NV NVRAM module support" 42 depends on MACH_DECSTATION 43 help 44 This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery 45 backed-up NVRAM module. The module was originally meant as an NFS 46 accelerator. Say Y here if you have a DECstation 5000/2x0 or a 47 DECsystem 5900 equipped with such a module. 48 49 If you want to compile this driver as a module ( = code which can be 50 inserted in and removed from the running kernel whenever you want), 51 say M here and read <file:Documentation/kbuild/modules.rst>. 52 The module will be called ms02-nv. 53 54config MTD_DATAFLASH 55 tristate "Support for AT45xxx DataFlash" 56 depends on SPI_MASTER 57 help 58 This enables access to AT45xxx DataFlash chips, using SPI. 59 Sometimes DataFlash chips are packaged inside MMC-format 60 cards; at this writing, the MMC stack won't handle those. 61 62config MTD_DATAFLASH_WRITE_VERIFY 63 bool "Verify DataFlash page writes" 64 depends on MTD_DATAFLASH 65 help 66 This adds an extra check when data is written to the flash. 67 It may help if you are verifying chip setup (timings etc) on 68 your board. There is a rare possibility that even though the 69 device thinks the write was successful, a bit could have been 70 flipped accidentally due to device wear or something else. 71 72config MTD_DATAFLASH_OTP 73 bool "DataFlash OTP support (Security Register)" 74 depends on MTD_DATAFLASH 75 help 76 Newer DataFlash chips (revisions C and D) support 128 bytes of 77 one-time-programmable (OTP) data. The first half may be written 78 (once) with up to 64 bytes of data, such as a serial number or 79 other key product data. The second half is programmed with a 80 unique-to-each-chip bit pattern at the factory. 81 82config MTD_M25P80 83 tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)" 84 depends on SPI_MASTER && MTD_SPI_NOR 85 select SPI_MEM 86 help 87 This enables access to most modern SPI flash chips, used for 88 program and data storage. Series supported include Atmel AT26DF, 89 Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X. Other chips 90 are supported as well. See the driver source for the current list, 91 or to add other chips. 92 93 Note that the original DataFlash chips (AT45 series, not AT26DF), 94 need an entirely different driver. 95 96 Set up your spi devices with the right board-specific platform data, 97 if you want to specify device partitioning or to use a device which 98 doesn't support the JEDEC ID instruction. 99 100config MTD_MCHP23K256 101 tristate "Microchip 23K256 SRAM" 102 depends on SPI_MASTER 103 help 104 This enables access to Microchip 23K256 SRAM chips, using SPI. 105 106 Set up your spi devices with the right board-specific 107 platform data, or a device tree description if you want to 108 specify device partitioning 109 110config MTD_SPEAR_SMI 111 tristate "SPEAR MTD NOR Support through SMI controller" 112 depends on PLAT_SPEAR 113 default y 114 help 115 This enable SNOR support on SPEAR platforms using SMI controller 116 117config MTD_SST25L 118 tristate "Support SST25L (non JEDEC) SPI Flash chips" 119 depends on SPI_MASTER 120 help 121 This enables access to the non JEDEC SST25L SPI flash chips, used 122 for program and data storage. 123 124 Set up your spi devices with the right board-specific platform data, 125 if you want to specify device partitioning. 126 127config MTD_BCM47XXSFLASH 128 tristate "Support for serial flash on BCMA bus" 129 depends on BCMA_SFLASH && (MIPS || ARM) 130 help 131 BCMA bus can have various flash memories attached, they are 132 registered by bcma as platform devices. This enables driver for 133 serial flash memories. 134 135config MTD_SLRAM 136 tristate "Uncached system RAM" 137 help 138 If your CPU cannot cache all of the physical memory in your machine, 139 you can still use it for storage or swap by using this driver to 140 present it to the system as a Memory Technology Device. 141 142config MTD_PHRAM 143 tristate "Physical system RAM" 144 help 145 This is a re-implementation of the slram driver above. 146 147 Use this driver to access physical memory that the kernel proper 148 doesn't have access to, memory beyond the mem=xxx limit, nvram, 149 memory on the video card, etc... 150 151config MTD_LART 152 tristate "28F160xx flash driver for LART" 153 depends on SA1100_LART 154 help 155 This enables the flash driver for LART. Please note that you do 156 not need any mapping/chip driver for LART. This one does it all 157 for you, so go disable all of those if you enabled some of them (: 158 159config MTD_MTDRAM 160 tristate "Test driver using RAM" 161 help 162 This enables a test MTD device driver which uses vmalloc() to 163 provide storage. You probably want to say 'N' unless you're 164 testing stuff. 165 166config MTDRAM_TOTAL_SIZE 167 int "MTDRAM device size in KiB" 168 depends on MTD_MTDRAM 169 default "4096" 170 help 171 This allows you to configure the total size of the MTD device 172 emulated by the MTDRAM driver. If the MTDRAM driver is built 173 as a module, it is also possible to specify this as a parameter when 174 loading the module. 175 176config MTDRAM_ERASE_SIZE 177 int "MTDRAM erase block size in KiB" 178 depends on MTD_MTDRAM 179 default "128" 180 help 181 This allows you to configure the size of the erase blocks in the 182 device emulated by the MTDRAM driver. If the MTDRAM driver is built 183 as a module, it is also possible to specify this as a parameter when 184 loading the module. 185 186config MTD_BLOCK2MTD 187 tristate "MTD using block device" 188 depends on BLOCK 189 help 190 This driver allows a block device to appear as an MTD. It would 191 generally be used in the following cases: 192 193 Using Compact Flash as an MTD, these usually present themselves to 194 the system as an ATA drive. 195 Testing MTD users (eg JFFS2) on large media and media that might 196 be removed during a write (using the floppy drive). 197 198config MTD_POWERNV_FLASH 199 tristate "powernv flash MTD driver" 200 depends on PPC_POWERNV 201 help 202 This provides an MTD device to access flash on powernv OPAL 203 platforms from Linux. This device abstracts away the 204 firmware interface for flash access. 205 206comment "Disk-On-Chip Device Drivers" 207 208config MTD_DOCG3 209 tristate "M-Systems Disk-On-Chip G3" 210 select BCH 211 select BCH_CONST_PARAMS if !MTD_NAND_ECC_SW_BCH 212 select BITREVERSE 213 help 214 This provides an MTD device driver for the M-Systems DiskOnChip 215 G3 devices. 216 217 The driver provides access to G3 DiskOnChip, distributed by 218 M-Systems and now Sandisk. The support is very experimental, 219 and doesn't give access to any write operations. 220 221config MTD_ST_SPI_FSM 222 tristate "ST Microelectronics SPI FSM Serial Flash Controller" 223 depends on ARCH_STI 224 help 225 This provides an MTD device driver for the ST Microelectronics 226 SPI Fast Sequence Mode (FSM) Serial Flash Controller and support 227 for a subset of connected Serial Flash devices. 228 229if MTD_DOCG3 230config BCH_CONST_M 231 default 14 232config BCH_CONST_T 233 default 4 234endif 235 236endmenu 237