Hi, 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. > > The intent is to later provide this information to the user space. > > Signed-off-by: Sakari Ailus <sakari.ailus@xxxxxxxxxxxxxxx> > Acked-by: Pavel Machek <pavel@xxxxxx> Reviewed-by: Sebastian Reichel <sebastian.reichel@xxxxxxxxxxxxxxx> > diff --git a/Documentation/devicetree/bindings/media/video-interfaces.txt b/Documentation/devicetree/bindings/media/video-interfaces.txt > index 0a33240..38e3916 100644 > --- a/Documentation/devicetree/bindings/media/video-interfaces.txt > +++ b/Documentation/devicetree/bindings/media/video-interfaces.txt > @@ -79,6 +79,9 @@ Optional properties > > - lens-focus: A phandle to the node of the focus lens controller. > > +- eeprom: A phandle to the node of the EEPROM describing the camera sensor > + (i.e. device specific calibration data), in case it differs from the > + sensor node. > > Optional endpoint properties > ---------------------------- -- Sebastian
Attachment:
signature.asc
Description: PGP signature
