[deliverable/linux.git] / drivers / misc / eeprom / Kconfig

menu "EEPROM support"

config AT24
	tristate "I2C EEPROMs from most vendors"
	depends on I2C && SYSFS && EXPERIMENTAL
	help
	  Enable this driver to get read/write support to most I2C EEPROMs,
	  after you configure the driver to know about each EEPROM on
	  your target board.  Use these generic chip names, instead of
	  vendor-specific ones like at24c64 or 24lc02:

	     24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08,
	     24c16, 24c32, 24c64, 24c128, 24c256, 24c512, 24c1024

	  Unless you like data loss puzzles, always be sure that any chip
	  you configure as a 24c32 (32 kbit) or larger is NOT really a
	  24c16 (16 kbit) or smaller, and vice versa. Marking the chip
	  as read-only won't help recover from this. Also, if your chip
	  has any software write-protect mechanism you may want to review the
	  code to make sure this driver won't turn it on by accident.

	  If you use this with an SMBus adapter instead of an I2C adapter,
	  full functionality is not available.  Only smaller devices are
	  supported (24c16 and below, max 4 kByte).

	  This driver can also be built as a module.  If so, the module
	  will be called at24.

config SPI_AT25
	tristate "SPI EEPROMs from most vendors"
	depends on SPI && SYSFS
	help
	  Enable this driver to get read/write support to most SPI EEPROMs,
	  after you configure the board init code to know about each eeprom
	  on your target board.

	  This driver can also be built as a module.  If so, the module
	  will be called at25.

config SENSORS_EEPROM
	tristate "Old I2C EEPROM reader"
	depends on I2C && EXPERIMENTAL
	help
	  If you say yes here you get read-only access to the EEPROM data
	  available on modern memory DIMMs and Sony Vaio laptops via I2C. Such
	  EEPROMs could theoretically be available on other devices as well.

	  This driver can also be built as a module.  If so, the module
	  will be called eeprom.

endmenu
Commit	Line	Data
5195e509 WS	1	menu "EEPROM support"
	2
	3	config AT24
	4	tristate "I2C EEPROMs from most vendors"
	5	depends on I2C && SYSFS && EXPERIMENTAL
	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
e51d565f WS	29	config SPI_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
2e157888 WS	40	config SENSORS_EEPROM
	41	tristate "Old I2C EEPROM reader"
	42	depends on I2C && EXPERIMENTAL
	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
5195e509	51	endmenu