1menu "EEPROM support"
 2
 3config EEPROM_AT24
 4	tristate "I2C EEPROMs from most vendors"
 5	depends on I2C && SYSFS
 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
29config EEPROM_AT25
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
40config EEPROM_LEGACY
41	tristate "Old I2C EEPROM reader"
42	depends on I2C && SYSFS
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
51config 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
65config 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
73config EEPROM_93XX46
74	tristate "Microwire EEPROM 93XX46 support"
75	depends on SPI && SYSFS
76	help
77	  Driver for the microwire EEPROM chipsets 93xx46x. The driver
78	  supports both read and write commands and also the command to
79	  erase the whole EEPROM.
80
81	  This driver can also be built as a module.  If so, the module
82	  will be called eeprom_93xx46.
83
84	  If unsure, say N.
85
86config EEPROM_DIGSY_MTC_CFG
87	bool "DigsyMTC display configuration EEPROMs device"
88	depends on PPC_MPC5200_GPIO && GPIOLIB && SPI_GPIO
89	help
90	  This option enables access to display configuration EEPROMs
91	  on digsy_mtc board. You have to additionally select Microwire
92	  EEPROM 93XX46 driver. sysfs entries will be created for that
93	  EEPROM allowing to read/write the configuration data or to
94	  erase the whole EEPROM.
95
96	  If unsure, say N.
 
 
 
 
 
 
 
 
 
 
 
 
 
97
98endmenu

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