Re: [PATCH RESEND v7 1/2] Add OV5647 device tree documentation
From: Sakari Ailus <sakari.ailus@linux.intel.com>
Date: 2017-02-03 20:19:28
Also in:
linux-media, lkml
Hi Ramiro, On Fri, Feb 03, 2017 at 06:18:32PM +0000, Ramiro Oliveira wrote:
quoted hunk ↗ jump to hunk
Create device tree bindings documentation. Signed-off-by: Ramiro Oliveira <redacted> Acked-by: Rob Herring <robh@kernel.org> --- .../devicetree/bindings/media/i2c/ov5647.txt | 35 ++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5647.txtdiff --git a/Documentation/devicetree/bindings/media/i2c/ov5647.txt b/Documentation/devicetree/bindings/media/i2c/ov5647.txt new file mode 100644 index 000000000000..57fd40036c26 --- /dev/null +++ b/Documentation/devicetree/bindings/media/i2c/ov5647.txt@@ -0,0 +1,35 @@ +Omnivision OV5647 raw image sensor +--------------------------------- + +OV5647 is a raw image sensor with MIPI CSI-2 and CCP2 image data interfaces +and CCI (I2C compatible) control bus. + +Required properties: + +- compatible : "ovti,ov5647". +- reg : I2C slave address of the sensor. +- clocks : Reference to the xclk clock. +- clock-names : Should be "xclk". +- clock-frequency : Frequency of the xclk clock. + +The common video interfaces bindings (see video-interfaces.txt) should be +used to specify link to the image data receiver. The OV5647 device +node should contain one 'port' child node with an 'endpoint' subnode. + +Example: + + i2c@2000 { + ... + ov: camera@36 { + compatible = "ovti,ov5647"; + reg = <0x36>; + clocks = <&camera_clk>; + clock-names = "xclk"; + clock-frequency = <30000000>;
For what it's worth, the spec documents the supported frequency range as 6--27 MHz. Most units could still work on frequencies slightly off the range though.
+ port {
+ camera_1: endpoint {
+ remote-endpoint = <&csi1_ep1>;
+ };
+ };
+ };
+ };-- Regards, Sakari Ailus sakari.ailus@linux.intel.com