From: Shunqian Zheng <zhengsq@rock-chips.com>
To: mchehab@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
ddl@rock-chips.com, tfiga@chromium.org,
Shunqian Zheng <zhengsq@rock-chips.com>
Subject: [PATCH 2/4] [media] dt/bindings: Add bindings for OV5695
Date: Mon, 25 Dec 2017 22:11:24 +0800 [thread overview]
Message-ID: <1514211086-13440-2-git-send-email-zhengsq@rock-chips.com> (raw)
In-Reply-To: <1514211086-13440-1-git-send-email-zhengsq@rock-chips.com>
Add device tree binding documentation for the OV5695 sensor.
Signed-off-by: Shunqian Zheng <zhengsq@rock-chips.com>
---
.../devicetree/bindings/media/i2c/ov5695.txt | 38 ++++++++++++++++++++++
1 file changed, 38 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5695.txt
diff --git a/Documentation/devicetree/bindings/media/i2c/ov5695.txt b/Documentation/devicetree/bindings/media/i2c/ov5695.txt
new file mode 100644
index 0000000..ed27eb1
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/i2c/ov5695.txt
@@ -0,0 +1,38 @@
+* Omnivision OV5695 MIPI CSI-2 sensor
+
+Required Properties:
+- compatible: should be "ovti,ov5695"
+- clocks: reference to the 24M xvclk input clock.
+- clock-names: should be "xvclk".
+- dovdd-supply: Digital I/O voltage supply, 1.8 volts
+- avdd-supply: Analog voltage supply, 2.8 volts
+- dvdd-supply: Digital core voltage supply, 1.2 volts
+- reset-gpios: Low active reset gpio
+
+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.
+
+Example:
+&i2c1 {
+ compatible = "ovti,ov5695";
+ reg = <0x36>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&clk_24m_cam &wcam_rst>;
+
+ clocks = <&cru SCLK_TESTCLKOUT1>;
+ clock-names = "xvclk";
+
+ avdd-supply = <&pp2800_cam>;
+ dvdd-supply = <&pp1250_cam>;
+ dovdd-supply = <&pp1800>;
+
+ reset-gpios = <&gpio2 5 GPIO_ACTIVE_LOW>;
+
+ port {
+ wcam_out: endpoint {
+ remote-endpoint = <&mipi_in_wcam>;
+ data-lanes = <1 2>;
+ };
+ };
+};
--
1.9.1
next prev parent reply other threads:[~2017-12-25 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-25 14:11 [PATCH 1/4] media: ov5695: add support for OV5695 sensor Shunqian Zheng
2017-12-25 14:11 ` Shunqian Zheng [this message]
2017-12-26 23:27 ` [PATCH 2/4] [media] dt/bindings: Add bindings for OV5695 Rob Herring
2017-12-25 14:11 ` [PATCH 3/4] media: ov2685: add support for OV2685 sensor Shunqian Zheng
[not found] ` <1514211086-13440-3-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-12-26 6:22 ` kbuild test robot
[not found] ` <1514211086-13440-1-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-12-25 14:11 ` [PATCH 4/4] [media] dt/bindings: Add bindings for OV2685 Shunqian Zheng
[not found] ` <1514211086-13440-4-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-12-26 23:28 ` Rob Herring
2017-12-27 0:40 ` Shunqian Zheng
2017-12-26 5:34 ` [PATCH 1/4] media: ov5695: add support for OV5695 sensor kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1514211086-13440-2-git-send-email-zhengsq@rock-chips.com \
--to=zhengsq@rock-chips.com \
--cc=ddl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tfiga@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).