Commit | Line | Data |
---|---|---|
5195e509 WS |
1 | menu "EEPROM support" |
2 | ||
dd7f8dbe | 3 | config EEPROM_AT24 |
5195e509 | 4 | tristate "I2C EEPROMs from most vendors" |
781b8a2a | 5 | depends on I2C && SYSFS |
5195e509 WS |
6 | help |
7 | Enable this driver to get read/write support to most I2C EEPROMs, | |
8 | after you configure the driver to know about each EEPROM on | |
9 | your target board. Use these generic chip names, instead of | |
10 | vendor-specific ones like at24c64 or 24lc02: | |
11 | ||
12 | 24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08, | |
13 | 24c16, 24c32, 24c64, 24c128, 24c256, 24c512, 24c1024 | |
14 | ||
15 | Unless you like data loss puzzles, always be sure that any chip | |
16 | you configure as a 24c32 (32 kbit) or larger is NOT really a | |
17 | 24c16 (16 kbit) or smaller, and vice versa. Marking the chip | |
18 | as read-only won't help recover from this. Also, if your chip | |
19 | has any software write-protect mechanism you may want to review the | |
20 | code to make sure this driver won't turn it on by accident. | |
21 | ||
22 | If you use this with an SMBus adapter instead of an I2C adapter, | |
23 | full functionality is not available. Only smaller devices are | |
24 | supported (24c16 and below, max 4 kByte). | |
25 | ||
26 | This driver can also be built as a module. If so, the module | |
27 | will be called at24. | |
28 | ||
dd7f8dbe | 29 | config EEPROM_AT25 |
e51d565f WS |
30 | tristate "SPI EEPROMs from most vendors" |
31 | depends on SPI && SYSFS | |
32 | help | |
33 | Enable this driver to get read/write support to most SPI EEPROMs, | |
34 | after you configure the board init code to know about each eeprom | |
35 | on your target board. | |
36 | ||
37 | This driver can also be built as a module. If so, the module | |
38 | will be called at25. | |
39 | ||
dd7f8dbe | 40 | config EEPROM_LEGACY |
2e157888 | 41 | tristate "Old I2C EEPROM reader" |
dd7f8dbe | 42 | depends on I2C && SYSFS |
2e157888 WS |
43 | help |
44 | If you say yes here you get read-only access to the EEPROM data | |
45 | available on modern memory DIMMs and Sony Vaio laptops via I2C. Such | |
46 | EEPROMs could theoretically be available on other devices as well. | |
47 | ||
48 | This driver can also be built as a module. If so, the module | |
49 | will be called eeprom. | |
50 | ||
4b364f23 WS |
51 | config EEPROM_MAX6875 |
52 | tristate "Maxim MAX6874/5 power supply supervisor" | |
53 | depends on I2C && EXPERIMENTAL | |
54 | help | |
55 | If you say yes here you get read-only support for the user EEPROM of | |
56 | the Maxim MAX6874/5 EEPROM-programmable, quad power-supply | |
57 | sequencer/supervisor. | |
58 | ||
59 | All other features of this chip should be accessed via i2c-dev. | |
60 | ||
61 | This driver can also be built as a module. If so, the module | |
62 | will be called max6875. | |
63 | ||
64 | ||
0eb6da20 WS |
65 | config EEPROM_93CX6 |
66 | tristate "EEPROM 93CX6 support" | |
67 | help | |
68 | This is a driver for the EEPROM chipsets 93c46 and 93c66. | |
69 | The driver supports both read as well as write commands. | |
70 | ||
71 | If unsure, say N. | |
72 | ||
5195e509 | 73 | endmenu |