projects / linux-2.6-block.git / blame
| Commit | Line | Data |
|---|---|---|
| ec8f24b7 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 5195e509 WS |
2 | menu "EEPROM support" |
| 3 | ||
| dd7f8dbe | 4 | config EEPROM_AT24 |
| 81e34f91 | 5 | tristate "I2C EEPROMs / RAMs / ROMs from most vendors" |
| 781b8a2a | 6 | depends on I2C && SYSFS |
| 57d15550 | 7 | select NVMEM |
| 5c015258 | 8 | select REGMAP_I2C |
| 5195e509 | 9 | help |
| 81e34f91 LP |
10 | Enable this driver to get read/write support to most I2C EEPROMs |
| 11 | and compatible devices like FRAMs, SRAMs, ROMs etc. After you | |
| 12 | configure the driver to know about each chip on your target | |
| 13 | board. Use these generic chip names, instead of vendor-specific | |
| 14 | ones like at24c64, 24lc02 or fm24c04: | |
| 5195e509 WS |
15 | |
| 16 | 24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08, | |
| 37cf28d3 | 17 | 24c16, 24c32, 24c64, 24c128, 24c256, 24c512, 24c1024, 24c2048 |
| 5195e509 WS |
18 | |
| 19 | Unless you like data loss puzzles, always be sure that any chip | |
| 20 | you configure as a 24c32 (32 kbit) or larger is NOT really a | |
| 21 | 24c16 (16 kbit) or smaller, and vice versa. Marking the chip | |
| 22 | as read-only won't help recover from this. Also, if your chip | |
| 23 | has any software write-protect mechanism you may want to review the | |
| 24 | code to make sure this driver won't turn it on by accident. | |
| 25 | ||
| 26 | If you use this with an SMBus adapter instead of an I2C adapter, | |
| 27 | full functionality is not available. Only smaller devices are | |
| 28 | supported (24c16 and below, max 4 kByte). | |
| 29 | ||
| 30 | This driver can also be built as a module. If so, the module | |
| 31 | will be called at24. | |
| 32 | ||
| dd7f8dbe | 33 | config EEPROM_AT25 |
| e51d565f WS |
34 | tristate "SPI EEPROMs from most vendors" |
| 35 | depends on SPI && SYSFS | |
| 5a99f570 | 36 | select NVMEM |
| e51d565f WS |
37 | help |
| 38 | Enable this driver to get read/write support to most SPI EEPROMs, | |
| 39 | after you configure the board init code to know about each eeprom | |
| 40 | on your target board. | |
| 41 | ||
| 42 | This driver can also be built as a module. If so, the module | |
| 43 | will be called at25. | |
| 44 | ||
| dd7f8dbe | 45 | config EEPROM_LEGACY |
| 2e157888 | 46 | tristate "Old I2C EEPROM reader" |
| dd7f8dbe | 47 | depends on I2C && SYSFS |
| 2e157888 WS |
48 | help |
| 49 | If you say yes here you get read-only access to the EEPROM data | |
| 50 | available on modern memory DIMMs and Sony Vaio laptops via I2C. Such | |
| 51 | EEPROMs could theoretically be available on other devices as well. | |
| 52 | ||
| 53 | This driver can also be built as a module. If so, the module | |
| 54 | will be called eeprom. | |
| 55 | ||
| 4b364f23 WS |
56 | config EEPROM_MAX6875 |
| 57 | tristate "Maxim MAX6874/5 power supply supervisor" | |
| 65929215 | 58 | depends on I2C |
| 4b364f23 WS |
59 | help |
| 60 | If you say yes here you get read-only support for the user EEPROM of | |
| 61 | the Maxim MAX6874/5 EEPROM-programmable, quad power-supply | |
| 62 | sequencer/supervisor. | |
| 63 | ||
| 64 | All other features of this chip should be accessed via i2c-dev. | |
| 65 | ||
| 66 | This driver can also be built as a module. If so, the module | |
| 67 | will be called max6875. | |
| 68 | ||
| 69 | ||
| 0eb6da20 WS |
70 | config EEPROM_93CX6 |
| 71 | tristate "EEPROM 93CX6 support" | |
| 72 | help | |
| 73 | This is a driver for the EEPROM chipsets 93c46 and 93c66. | |
| 74 | The driver supports both read as well as write commands. | |
| 75 | ||
| 76 | If unsure, say N. | |
| 77 | ||
| 06b4501e AG |
78 | config EEPROM_93XX46 |
| 79 | tristate "Microwire EEPROM 93XX46 support" | |
| 80 | depends on SPI && SYSFS | |
| 1c4b6e2c AL |
81 | select REGMAP |
| 82 | select NVMEM | |
| 06b4501e AG |
83 | help |
| 84 | Driver for the microwire EEPROM chipsets 93xx46x. The driver | |
| 85 | supports both read and write commands and also the command to | |
| 86 | erase the whole EEPROM. | |
| 87 | ||
| 88 | This driver can also be built as a module. If so, the module | |
| 89 | will be called eeprom_93xx46. | |
| 90 | ||
| 91 | If unsure, say N. | |
| 92 | ||
| 469dded1 AG |
93 | config EEPROM_DIGSY_MTC_CFG |
| 94 | bool "DigsyMTC display configuration EEPROMs device" | |
| 001ef5e4 | 95 | depends on GPIO_MPC5200 && SPI_GPIO |
| 469dded1 AG |
96 | help |
| 97 | This option enables access to display configuration EEPROMs | |
| 98 | on digsy_mtc board. You have to additionally select Microwire | |
| 99 | EEPROM 93XX46 driver. sysfs entries will be created for that | |
| 100 | EEPROM allowing to read/write the configuration data or to | |
| 101 | erase the whole EEPROM. | |
| 102 | ||
| 103 | If unsure, say N. | |
| 104 | ||
| cfad6425 SS |
105 | config EEPROM_IDT_89HPESX |
| 106 | tristate "IDT 89HPESx PCIe-swtiches EEPROM / CSR support" | |
| 107 | depends on I2C && SYSFS | |
| 108 | help | |
| 109 | Enable this driver to get read/write access to EEPROM / CSRs | |
| 110 | over IDT PCIe-swtich i2c-slave interface. | |
| 111 | ||
| 112 | This driver can also be built as a module. If so, the module | |
| 113 | will be called idt_89hpesx. | |
| 114 | ||
| 3b7584a2 JD |
115 | config EEPROM_EE1004 |
| 116 | tristate "SPD EEPROMs on DDR4 memory modules" | |
| 117 | depends on I2C && SYSFS | |
| 118 | help | |
| 119 | Enable this driver to get read support to SPD EEPROMs following | |
| 120 | the JEDEC EE1004 standard. These are typically found on DDR4 | |
| 121 | SDRAM memory modules. | |
| 122 | ||
| 123 | This driver can also be built as a module. If so, the module | |
| 124 | will be called ee1004. | |
| 125 | ||
| 5195e509 | 126 | endmenu |