1*5195e509SWolfram Sangmenu "EEPROM support" 2*5195e509SWolfram Sang 3*5195e509SWolfram Sangconfig AT24 4*5195e509SWolfram Sang tristate "I2C EEPROMs from most vendors" 5*5195e509SWolfram Sang depends on I2C && SYSFS && EXPERIMENTAL 6*5195e509SWolfram Sang help 7*5195e509SWolfram Sang Enable this driver to get read/write support to most I2C EEPROMs, 8*5195e509SWolfram Sang after you configure the driver to know about each EEPROM on 9*5195e509SWolfram Sang your target board. Use these generic chip names, instead of 10*5195e509SWolfram Sang vendor-specific ones like at24c64 or 24lc02: 11*5195e509SWolfram Sang 12*5195e509SWolfram Sang 24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08, 13*5195e509SWolfram Sang 24c16, 24c32, 24c64, 24c128, 24c256, 24c512, 24c1024 14*5195e509SWolfram Sang 15*5195e509SWolfram Sang Unless you like data loss puzzles, always be sure that any chip 16*5195e509SWolfram Sang you configure as a 24c32 (32 kbit) or larger is NOT really a 17*5195e509SWolfram Sang 24c16 (16 kbit) or smaller, and vice versa. Marking the chip 18*5195e509SWolfram Sang as read-only won't help recover from this. Also, if your chip 19*5195e509SWolfram Sang has any software write-protect mechanism you may want to review the 20*5195e509SWolfram Sang code to make sure this driver won't turn it on by accident. 21*5195e509SWolfram Sang 22*5195e509SWolfram Sang If you use this with an SMBus adapter instead of an I2C adapter, 23*5195e509SWolfram Sang full functionality is not available. Only smaller devices are 24*5195e509SWolfram Sang supported (24c16 and below, max 4 kByte). 25*5195e509SWolfram Sang 26*5195e509SWolfram Sang This driver can also be built as a module. If so, the module 27*5195e509SWolfram Sang will be called at24. 28*5195e509SWolfram Sang 29*5195e509SWolfram Sangendmenu 30