217 lines · plain
1# SPDX-License-Identifier: GPL-2.0-only2menu "Self-contained MTD device drivers"3 depends on MTD!=n4 depends on HAS_IOMEM5 6config MTD_PMC5517 tristate "Ramix PMC551 PCI Mezzanine RAM card support"8 depends on PCI9 help10 This provides a MTD device driver for the Ramix PMC551 RAM PCI card11 from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.12 These devices come in memory configurations from 32M - 1G. If you13 have one, you probably want to enable this.14 15 If this driver is compiled as a module you get the ability to select16 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 kernel18 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 will20 "slide" the window around the PMC551's memory. This was21 particularly useful on the 2.2 kernels on PPC architectures as there22 was limited kernel space to deal with.23 24config MTD_PMC551_BUGFIX25 bool "PMC551 256M DRAM Bugfix"26 depends on MTD_PMC55127 help28 Some of Ramix's PMC551 boards with 256M configurations have invalid29 column and row mux values. This option will fix them, but will30 break other memory configurations. If unsure say N.31 32config MTD_PMC551_DEBUG33 bool "PMC551 Debugging"34 depends on MTD_PMC55135 help36 This option makes the PMC551 more verbose during its operation and37 is only really useful if you are developing on this driver or38 suspect a possible hardware or driver bug. If unsure say N.39 40config MTD_MS02NV41 tristate "DEC MS02-NV NVRAM module support"42 depends on MACH_DECSTATION43 help44 This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery45 backed-up NVRAM module. The module was originally meant as an NFS46 accelerator. Say Y here if you have a DECstation 5000/2x0 or a47 DECsystem 5900 equipped with such a module.48 49 If you want to compile this driver as a module ( = code which can be50 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_DATAFLASH55 tristate "Support for AT45xxx DataFlash"56 depends on SPI_MASTER57 help58 This enables access to AT45xxx DataFlash chips, using SPI.59 Sometimes DataFlash chips are packaged inside MMC-format60 cards; at this writing, the MMC stack won't handle those.61 62config MTD_DATAFLASH_WRITE_VERIFY63 bool "Verify DataFlash page writes"64 depends on MTD_DATAFLASH65 help66 This adds an extra check when data is written to the flash.67 It may help if you are verifying chip setup (timings etc) on68 your board. There is a rare possibility that even though the69 device thinks the write was successful, a bit could have been70 flipped accidentally due to device wear or something else.71 72config MTD_DATAFLASH_OTP73 bool "DataFlash OTP support (Security Register)"74 depends on MTD_DATAFLASH75 help76 Newer DataFlash chips (revisions C and D) support 128 bytes of77 one-time-programmable (OTP) data. The first half may be written78 (once) with up to 64 bytes of data, such as a serial number or79 other key product data. The second half is programmed with a80 unique-to-each-chip bit pattern at the factory.81 82config MTD_MCHP23K25683 tristate "Microchip 23K256 SRAM"84 depends on SPI_MASTER85 help86 This enables access to Microchip 23K256 SRAM chips, using SPI.87 88 Set up your spi devices with the right board-specific89 platform data, or a device tree description if you want to90 specify device partitioning91 92config MTD_MCHP48L64093 tristate "Microchip 48L640 EERAM"94 depends on SPI_MASTER95 help96 This enables access to Microchip 48L640 EERAM chips, using SPI.97 98config MTD_SPEAR_SMI99 tristate "SPEAR MTD NOR Support through SMI controller"100 depends on PLAT_SPEAR || COMPILE_TEST101 default y102 help103 This enable SNOR support on SPEAR platforms using SMI controller104 105config MTD_SST25L106 tristate "Support SST25L (non JEDEC) SPI Flash chips"107 depends on SPI_MASTER108 help109 This enables access to the non JEDEC SST25L SPI flash chips, used110 for program and data storage.111 112 Set up your spi devices with the right board-specific platform data,113 if you want to specify device partitioning.114 115config MTD_BCM47XXSFLASH116 tristate "Support for serial flash on BCMA bus"117 depends on BCMA_SFLASH && (MIPS || ARM)118 help119 BCMA bus can have various flash memories attached, they are120 registered by bcma as platform devices. This enables driver for121 serial flash memories.122 123config MTD_SLRAM124 tristate "Uncached system RAM"125 help126 If your CPU cannot cache all of the physical memory in your machine,127 you can still use it for storage or swap by using this driver to128 present it to the system as a Memory Technology Device.129 130config MTD_PHRAM131 tristate "Physical system RAM"132 help133 This is a re-implementation of the slram driver above.134 135 Use this driver to access physical memory that the kernel proper136 doesn't have access to, memory beyond the mem=xxx limit, nvram,137 memory on the video card, etc...138 139config MTD_MTDRAM140 tristate "Test driver using RAM"141 help142 This enables a test MTD device driver which uses vmalloc() to143 provide storage. You probably want to say 'N' unless you're144 testing stuff.145 146config MTDRAM_TOTAL_SIZE147 int "MTDRAM device size in KiB"148 depends on MTD_MTDRAM149 default "4096"150 help151 This allows you to configure the total size of the MTD device152 emulated by the MTDRAM driver. If the MTDRAM driver is built153 as a module, it is also possible to specify this as a parameter when154 loading the module.155 156config MTDRAM_ERASE_SIZE157 int "MTDRAM erase block size in KiB"158 depends on MTD_MTDRAM159 default "128"160 help161 This allows you to configure the size of the erase blocks in the162 device emulated by the MTDRAM driver. If the MTDRAM driver is built163 as a module, it is also possible to specify this as a parameter when164 loading the module.165 166config MTD_BLOCK2MTD167 tristate "MTD using block device"168 depends on BLOCK169 help170 This driver allows a block device to appear as an MTD. It would171 generally be used in the following cases:172 173 Using Compact Flash as an MTD, these usually present themselves to174 the system as an ATA drive.175 Testing MTD users (eg JFFS2) on large media and media that might176 be removed during a write (using the floppy drive).177 178config MTD_POWERNV_FLASH179 tristate "powernv flash MTD driver"180 depends on PPC_POWERNV181 help182 This provides an MTD device to access flash on powernv OPAL183 platforms from Linux. This device abstracts away the184 firmware interface for flash access.185 186comment "Disk-On-Chip Device Drivers"187 188config MTD_DOCG3189 tristate "M-Systems Disk-On-Chip G3"190 select BCH191 select BCH_CONST_PARAMS if !MTD_NAND_ECC_SW_BCH192 select BITREVERSE193 help194 This provides an MTD device driver for the M-Systems DiskOnChip195 G3 devices.196 197 The driver provides access to G3 DiskOnChip, distributed by198 M-Systems and now Sandisk. The support is very experimental,199 and doesn't give access to any write operations.200 201config MTD_ST_SPI_FSM202 tristate "ST Microelectronics SPI FSM Serial Flash Controller"203 depends on ARCH_STI204 help205 This provides an MTD device driver for the ST Microelectronics206 SPI Fast Sequence Mode (FSM) Serial Flash Controller and support207 for a subset of connected Serial Flash devices.208 209if MTD_DOCG3210config BCH_CONST_M211 default 14212config BCH_CONST_T213 default 4214endif215 216endmenu217