On Thu, Jun 22, 2017 at 05:05:37PM +0200, Hugues Fruchet wrote: > From: "H. Nikolaus Schaller" <hns@xxxxxxxxxxxxx> > > This adds documentation of device tree bindings > for the OV965X family camera sensor module. > > Signed-off-by: H. Nikolaus Schaller <hns@xxxxxxxxxxxxx> > Signed-off-by: Hugues Fruchet <hugues.fruchet@xxxxxx> > --- > .../devicetree/bindings/media/i2c/ov965x.txt | 37 ++++++++++++++++++++++ > 1 file changed, 37 insertions(+) > create mode 100644 Documentation/devicetree/bindings/media/i2c/ov965x.txt > > diff --git a/Documentation/devicetree/bindings/media/i2c/ov965x.txt b/Documentation/devicetree/bindings/media/i2c/ov965x.txt > new file mode 100644 > index 0000000..0e0de1f > --- /dev/null > +++ b/Documentation/devicetree/bindings/media/i2c/ov965x.txt > @@ -0,0 +1,37 @@ > +* Omnivision OV9650/9652/9655 CMOS sensor > + > +The Omnivision OV965x sensor support multiple resolutions output, such as > +CIF, SVGA, UXGA. It also can support YUV422/420, RGB565/555 or raw RGB > +output format. > + > +Required Properties: > +- compatible: should be one of > + "ovti,ov9650" > + "ovti,ov9652" > + "ovti,ov9655" > +- clocks: reference to the mclk input clock. > + > +Optional Properties: > +- resetb-gpios: reference to the GPIO connected to the resetb pin, if any. reset-gpios and state it is active low. > +- pwdn-gpios: reference to the GPIO connected to the pwdn pin, if any. powerdown-gpios and state it is active ???. Those are semi-standard names. With that, Acked-by: Rob Herring <robh@xxxxxxxxxx>
