On Fri, May 05, 2017 at 11:48:30AM +0300, Sakari Ailus wrote: > Many camera sensor devices contain EEPROM chips that describe the > properties of a given unit --- the data is specific to a given unit can > thus is not stored e.g. in user space or the driver. > > Some sensors embed the EEPROM chip and it can be accessed through the > sensor's I2C interface. This property is to be used for devices where the > EEPROM chip is accessed through a different I2C address than the sensor. Different I2C address or bus? We already have i2c bindings for sub devices downstream of another I2C device. Either the upstream device passes thru the I2C transactions or itself is an I2C controller with a separate downstream bus. For those cases the EEPROM should be a child node. A phandle only makes sense if you have the sensor and eeprom connected to 2 entirely separate host buses. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
