xref: /openbmc/linux/drivers/misc/eeprom/Kconfig (revision fa0a497b)
1menu "EEPROM support"
2
3config EEPROM_AT24
4	tristate "I2C EEPROMs / RAMs / ROMs from most vendors"
5	depends on I2C && SYSFS
6	select REGMAP
7	select NVMEM
8	help
9	  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:
14
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
32config EEPROM_AT25
33	tristate "SPI EEPROMs from most vendors"
34	depends on SPI && SYSFS
35	select REGMAP
36	select NVMEM
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
45config EEPROM_LEGACY
46	tristate "Old I2C EEPROM reader"
47	depends on I2C && SYSFS
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
56config EEPROM_MAX6875
57	tristate "Maxim MAX6874/5 power supply supervisor"
58	depends on I2C
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
70config 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
78config EEPROM_93XX46
79	tristate "Microwire EEPROM 93XX46 support"
80	depends on SPI && SYSFS
81	select REGMAP
82	select NVMEM
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
93config EEPROM_DIGSY_MTC_CFG
94	bool "DigsyMTC display configuration EEPROMs device"
95	depends on GPIO_MPC5200 && SPI_GPIO
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
105endmenu
106