blob: cfc493c2e30a725695c50326dbfd9db170e0cfd1 [file] [log] [blame]
Wolfram Sang5195e502009-01-26 21:19:53 +01001menu "EEPROM support"
2
Jean Delvaredd7f8db2009-01-26 21:19:57 +01003config EEPROM_AT24
Lars Poeschel81e34f92012-12-05 10:43:07 +01004 tristate "I2C EEPROMs / RAMs / ROMs from most vendors"
Wolfram Sang781b8a22009-03-28 21:34:41 +01005 depends on I2C && SYSFS
Andrew Lunn57d15552016-02-26 20:59:20 +01006 select REGMAP
7 select NVMEM
Wolfram Sang5195e502009-01-26 21:19:53 +01008 help
Lars Poeschel81e34f92012-12-05 10:43:07 +01009 Enable this driver to get read/write support to most I2C EEPROMs
10 and compatible devices like FRAMs, SRAMs, ROMs etc. After you
11 configure the driver to know about each chip on your target
12 board. Use these generic chip names, instead of vendor-specific
13 ones like at24c64, 24lc02 or fm24c04:
Wolfram Sang5195e502009-01-26 21:19:53 +010014
15 24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08,
16 24c16, 24c32, 24c64, 24c128, 24c256, 24c512, 24c1024
17
18 Unless you like data loss puzzles, always be sure that any chip
19 you configure as a 24c32 (32 kbit) or larger is NOT really a
20 24c16 (16 kbit) or smaller, and vice versa. Marking the chip
21 as read-only won't help recover from this. Also, if your chip
22 has any software write-protect mechanism you may want to review the
23 code to make sure this driver won't turn it on by accident.
24
25 If you use this with an SMBus adapter instead of an I2C adapter,
26 full functionality is not available. Only smaller devices are
27 supported (24c16 and below, max 4 kByte).
28
29 This driver can also be built as a module. If so, the module
30 will be called at24.
31
Jean Delvaredd7f8db2009-01-26 21:19:57 +010032config EEPROM_AT25
Wolfram Sange51d5652009-01-26 21:19:54 +010033 tristate "SPI EEPROMs from most vendors"
34 depends on SPI && SYSFS
Andrew Lunn5a99f572016-02-26 20:59:22 +010035 select REGMAP
36 select NVMEM
Wolfram Sange51d5652009-01-26 21:19:54 +010037 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
Jean Delvaredd7f8db2009-01-26 21:19:57 +010045config EEPROM_LEGACY
Wolfram Sang2e157882009-01-26 21:19:53 +010046 tristate "Old I2C EEPROM reader"
Jean Delvaredd7f8db2009-01-26 21:19:57 +010047 depends on I2C && SYSFS
Wolfram Sang2e157882009-01-26 21:19:53 +010048 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
Wolfram Sang4b364f22009-06-15 18:01:49 +020056config EEPROM_MAX6875
57 tristate "Maxim MAX6874/5 power supply supervisor"
Greg Kroah-Hartman65929212012-09-18 16:14:53 +010058 depends on I2C
Wolfram Sang4b364f22009-06-15 18:01:49 +020059 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
Wolfram Sang0eb6da22009-01-26 21:19:54 +010070config 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
Anatolij Gustschin06b45012011-07-25 17:13:27 -070078config EEPROM_93XX46
79 tristate "Microwire EEPROM 93XX46 support"
80 depends on SPI && SYSFS
Andrew Lunn1c4b6e22016-02-26 20:59:23 +010081 select REGMAP
82 select NVMEM
Anatolij Gustschin06b45012011-07-25 17:13:27 -070083 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
Anatolij Gustschin469dded2011-07-25 17:13:29 -070093config EEPROM_DIGSY_MTC_CFG
94 bool "DigsyMTC display configuration EEPROMs device"
Paul Bolle001ef5e2011-11-15 14:36:02 -080095 depends on GPIO_MPC5200 && SPI_GPIO
Anatolij Gustschin469dded2011-07-25 17:13:29 -070096 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
Wolfram Sang5195e502009-01-26 21:19:53 +0100105endmenu