Hi Andy, On Wed, 05 Jan 2011 20:20:35 -0500, Andy Walls wrote: > The cx18 driver has a function scope i2c_client for reading the EEPROM, > and there's a good reason for it. We don't want to register the EEPROM > with the I2C system and make it visible to the rest of the system, > including i2c-dev and user-space tools. To avoid EEPROM corruption, > it's better keep communication with EEPROMs to a very limited scope. Note that it is possible to declare a read-only EEPROM, so that user-space has no chance to write to it. If you really don't want user-space to touch it, the best approach is i2c_new_dummy(), because it will mark the slave address as busy, preventing i2c-dev from accessing it (unless the user forces access - but then he/she is obviously on his/her own...) The i2c_client provided by i2c_new_dummy() can be unregistered at the end of the function which needs it, or kept for the lifetime of the driver, as you prefer. -- Jean Delvare -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
