xref: /openbmc/linux/drivers/misc/eeprom/Kconfig (revision ba61bb17)
1menu "EEPROM support"
2
3config EEPROM_AT24
4	tristate "I2C EEPROMs / RAMs / ROMs from most vendors"
5	depends on I2C && SYSFS
6	select NVMEM
7	select REGMAP_I2C
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 NVMEM
36	help
37	  Enable this driver to get read/write support to most SPI EEPROMs,
38	  after you configure the board init code to know about each eeprom
39	  on your target board.
40
41	  This driver can also be built as a module.  If so, the module
42	  will be called at25.
43
44config EEPROM_LEGACY
45	tristate "Old I2C EEPROM reader"
46	depends on I2C && SYSFS
47	help
48	  If you say yes here you get read-only access to the EEPROM data
49	  available on modern memory DIMMs and Sony Vaio laptops via I2C. Such
50	  EEPROMs could theoretically be available on other devices as well.
51
52	  This driver can also be built as a module.  If so, the module
53	  will be called eeprom.
54
55config EEPROM_MAX6875
56	tristate "Maxim MAX6874/5 power supply supervisor"
57	depends on I2C
58	help
59	  If you say yes here you get read-only support for the user EEPROM of
60	  the Maxim MAX6874/5 EEPROM-programmable, quad power-supply
61	  sequencer/supervisor.
62
63	  All other features of this chip should be accessed via i2c-dev.
64
65	  This driver can also be built as a module.  If so, the module
66	  will be called max6875.
67
68
69config EEPROM_93CX6
70	tristate "EEPROM 93CX6 support"
71	help
72	  This is a driver for the EEPROM chipsets 93c46 and 93c66.
73	  The driver supports both read as well as write commands.
74
75	  If unsure, say N.
76
77config EEPROM_93XX46
78	tristate "Microwire EEPROM 93XX46 support"
79	depends on SPI && SYSFS
80	select REGMAP
81	select NVMEM
82	help
83	  Driver for the microwire EEPROM chipsets 93xx46x. The driver
84	  supports both read and write commands and also the command to
85	  erase the whole EEPROM.
86
87	  This driver can also be built as a module.  If so, the module
88	  will be called eeprom_93xx46.
89
90	  If unsure, say N.
91
92config EEPROM_DIGSY_MTC_CFG
93	bool "DigsyMTC display configuration EEPROMs device"
94	depends on GPIO_MPC5200 && SPI_GPIO
95	help
96	  This option enables access to display configuration EEPROMs
97	  on digsy_mtc board. You have to additionally select Microwire
98	  EEPROM 93XX46 driver. sysfs entries will be created for that
99	  EEPROM allowing to read/write the configuration data or to
100	  erase the whole EEPROM.
101
102	  If unsure, say N.
103
104config EEPROM_IDT_89HPESX
105	tristate "IDT 89HPESx PCIe-swtiches EEPROM / CSR support"
106	depends on I2C && SYSFS
107	help
108	  Enable this driver to get read/write access to EEPROM / CSRs
109	  over IDT PCIe-swtich i2c-slave interface.
110
111	  This driver can also be built as a module. If so, the module
112	  will be called idt_89hpesx.
113
114endmenu
115