xref: /linux/drivers/misc/eeprom/Kconfig (revision b6ebbac51bedf9e98e837688bc838f400196da5e)
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	help
8	  Enable this driver to get read/write support to most I2C EEPROMs
9	  and compatible devices like FRAMs, SRAMs, ROMs etc. After you
10	  configure the driver to know about each chip on your target
11	  board.  Use these generic chip names, instead of vendor-specific
12	  ones like at24c64, 24lc02 or fm24c04:
13
14	     24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08,
15	     24c16, 24c32, 24c64, 24c128, 24c256, 24c512, 24c1024
16
17	  Unless you like data loss puzzles, always be sure that any chip
18	  you configure as a 24c32 (32 kbit) or larger is NOT really a
19	  24c16 (16 kbit) or smaller, and vice versa. Marking the chip
20	  as read-only won't help recover from this. Also, if your chip
21	  has any software write-protect mechanism you may want to review the
22	  code to make sure this driver won't turn it on by accident.
23
24	  If you use this with an SMBus adapter instead of an I2C adapter,
25	  full functionality is not available.  Only smaller devices are
26	  supported (24c16 and below, max 4 kByte).
27
28	  This driver can also be built as a module.  If so, the module
29	  will be called at24.
30
31config EEPROM_AT25
32	tristate "SPI EEPROMs from most vendors"
33	depends on SPI && SYSFS
34	select NVMEM
35	help
36	  Enable this driver to get read/write support to most SPI EEPROMs,
37	  after you configure the board init code to know about each eeprom
38	  on your target board.
39
40	  This driver can also be built as a module.  If so, the module
41	  will be called at25.
42
43config EEPROM_LEGACY
44	tristate "Old I2C EEPROM reader"
45	depends on I2C && SYSFS
46	help
47	  If you say yes here you get read-only access to the EEPROM data
48	  available on modern memory DIMMs and Sony Vaio laptops via I2C. Such
49	  EEPROMs could theoretically be available on other devices as well.
50
51	  This driver can also be built as a module.  If so, the module
52	  will be called eeprom.
53
54config EEPROM_MAX6875
55	tristate "Maxim MAX6874/5 power supply supervisor"
56	depends on I2C
57	help
58	  If you say yes here you get read-only support for the user EEPROM of
59	  the Maxim MAX6874/5 EEPROM-programmable, quad power-supply
60	  sequencer/supervisor.
61
62	  All other features of this chip should be accessed via i2c-dev.
63
64	  This driver can also be built as a module.  If so, the module
65	  will be called max6875.
66
67
68config EEPROM_93CX6
69	tristate "EEPROM 93CX6 support"
70	help
71	  This is a driver for the EEPROM chipsets 93c46 and 93c66.
72	  The driver supports both read as well as write commands.
73
74	  If unsure, say N.
75
76config EEPROM_93XX46
77	tristate "Microwire EEPROM 93XX46 support"
78	depends on SPI && SYSFS
79	select REGMAP
80	select NVMEM
81	help
82	  Driver for the microwire EEPROM chipsets 93xx46x. The driver
83	  supports both read and write commands and also the command to
84	  erase the whole EEPROM.
85
86	  This driver can also be built as a module.  If so, the module
87	  will be called eeprom_93xx46.
88
89	  If unsure, say N.
90
91config EEPROM_DIGSY_MTC_CFG
92	bool "DigsyMTC display configuration EEPROMs device"
93	depends on GPIO_MPC5200 && SPI_GPIO
94	help
95	  This option enables access to display configuration EEPROMs
96	  on digsy_mtc board. You have to additionally select Microwire
97	  EEPROM 93XX46 driver. sysfs entries will be created for that
98	  EEPROM allowing to read/write the configuration data or to
99	  erase the whole EEPROM.
100
101	  If unsure, say N.
102
103endmenu
104