diff options
author | Wolfram Sang <w.sang@pengutronix.de> | 2009-01-26 15:19:53 -0500 |
---|---|---|
committer | Jean Delvare <khali@linux-fr.org> | 2009-01-26 15:19:53 -0500 |
commit | 5195e5093bb7d30dbf057b260005cb4ab9761168 (patch) | |
tree | b73c91ea07ad4b6415461fdad8f217b5f721b274 /drivers/misc/eeprom/Kconfig | |
parent | a01064a92a1125995fd9078c2305df89a63ed9fe (diff) |
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 000000000000..0b21778b7d13 --- /dev/null +++ b/drivers/misc/eeprom/Kconfig | |||
@@ -0,0 +1,29 @@ | |||
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 | |||
29 | endmenu | ||