diff options
author | Wolfram Sang <w.sang@pengutronix.de> | 2009-01-26 20:19:53 (GMT) |
---|---|---|
committer | Jean Delvare <khali@linux-fr.org> | 2009-01-26 20:19:53 (GMT) |
commit | 5195e5093bb7d30dbf057b260005cb4ab9761168 (patch) | |
tree | b73c91ea07ad4b6415461fdad8f217b5f721b274 /drivers/misc/eeprom/Kconfig | |
parent | a01064a92a1125995fd9078c2305df89a63ed9fe (diff) | |
download | linux-fsl-qoriq-5195e5093bb7d30dbf057b260005cb4ab9761168.tar.xz |
i2c: Move at24 to drivers/misc/eeprom
As drivers/i2c/chips is going to go away, move the driver to
drivers/misc/eeprom. Other eeprom drivers may be moved here later, too.
Update Kconfig text to specify this driver as I2C.
Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Diffstat (limited to 'drivers/misc/eeprom/Kconfig')
-rw-r--r-- | drivers/misc/eeprom/Kconfig | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/drivers/misc/eeprom/Kconfig b/drivers/misc/eeprom/Kconfig new file mode 100644 index 0000000..0b21778 --- /dev/null +++ b/drivers/misc/eeprom/Kconfig @@ -0,0 +1,29 @@ +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. + +endmenu |