On Wed, May 18, 2016 at 02:50:07PM +0300, Todor Tomov wrote: > Add the document for ov5645 device tree binding. > > Signed-off-by: Todor Tomov <todor.to...@linaro.org> > --- > .../devicetree/bindings/media/i2c/ov5645.txt | 56 > ++++++++++++++++++++++ > 1 file changed, 56 insertions(+) > create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5645.txt > > diff --git a/Documentation/devicetree/bindings/media/i2c/ov5645.txt > b/Documentation/devicetree/bindings/media/i2c/ov5645.txt > new file mode 100644 > index 0000000..8799000 > --- /dev/null > +++ b/Documentation/devicetree/bindings/media/i2c/ov5645.txt > @@ -0,0 +1,56 @@ > +* Omnivision 1/4-Inch 5Mp CMOS Digital Image Sensor > + > +The Omnivision OV5645 is a 1/4-Inch CMOS active pixel digital image sensor > with > +an active array size of 2592H x 1944V. It is programmable through a serial > SCCB
s/SCCB/I2C/ because that is the more common name. > +interface. > + > +Required Properties: > +- compatible: value should be "ovti,ov5645" > +- clocks: reference to the xclk clock > +- clock-names: should be "xclk" > +- assigned-clocks: reference to the xclk clock This should be optional as it only makes sense if there is more than one option. > +- assigned-clock-rates: should be "23880000" Doesn't this depend on the board? Most parts take a range of frequencies. The driver should know what the range is and request a rate within this range. > + > +Optional Properties: > +- reset-gpios: Chip reset GPIO > +- pwdn-gpios: Chip power down GPIO Use enable-gpios as it is more common and would just be the inverse of this. Both need to specify the polarity. > +- dovdd-supply: Chip IO regulator > +- dvdd-supply: Chip core regulator > +- avdd-supply: Chip analog regulator > + > +The device node must contain one 'port' child node for its digital output > +video port, in accordance with the video interface bindings defined in > +Documentation/devicetree/bindings/media/video-interfaces.txt. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
