From: Jacob Chen <jacob-chen@iotwrt.com>
To: linux-rockchip@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, mchehab@kernel.org,
linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
hans.verkuil@cisco.com, tfiga@chromium.org,
zhengsq@rock-chips.com, laurent.pinchart@ideasonboard.com,
zyc@rock-chips.com, eddie.cai.linux@gmail.com,
jeffy.chen@rock-chips.com, allon.huang@rock-chips.com,
devicetree@vger.kernel.org, heiko@sntech.de, robh+dt@kernel.org,
Jacob Chen <jacob-chen@iotwrt.com>,
Jacob Chen <jacob2.chen@rock-chips.com>
Subject: [PATCH v2 06/11] dt-bindings: Document the Rockchip MIPI RX D-PHY bindings
Date: Fri, 24 Nov 2017 10:37:01 +0800 [thread overview]
Message-ID: <20171124023706.5702-7-jacob-chen@iotwrt.com> (raw)
In-Reply-To: <20171124023706.5702-1-jacob-chen@iotwrt.com>
Add DT bindings documentation for Rockchip MIPI D-PHY RX
Signed-off-by: Jacob Chen <jacob2.chen@rock-chips.com>
---
.../bindings/media/rockchip-mipi-dphy.txt | 77 ++++++++++++++++++++++
1 file changed, 77 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/rockchip-mipi-dphy.txt
diff --git a/Documentation/devicetree/bindings/media/rockchip-mipi-dphy.txt b/Documentation/devicetree/bindings/media/rockchip-mipi-dphy.txt
new file mode 100644
index 000000000000..b5773b67c250
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/rockchip-mipi-dphy.txt
@@ -0,0 +1,77 @@
+Rockchip SoC MIPI RX D-PHY
+-------------------------------------------------------------
+
+Required properties:
+
+- compatible: value should be one of the following
+ "rockchip,rk3288-mipi-dphy";
+ "rockchip,rk3399-mipi-dphy";
+- rockchip,grf: GRF regs.
+- bus-width : maximum number of data lanes supported (SoC specific);
+- clocks : list of clock specifiers, corresponding to entries in
+ clock-names property;
+- clock-names: required clock name.
+
+The device node should contain two 'port' child node, according to the bindings
+defined in Documentation/devicetree/bindings/media/video-interfaces.txt.
+The first port should be connected to sensor nodes, and the second port should be
+connected to isp node. The following are properties specific to those nodes.
+
+endpoint node
+-------------
+
+- data-lanes : (required) an array specifying active physical MIPI-CSI2
+ data input lanes and their mapping to logical lanes; the
+ array's content is unused, only its length is meaningful;
+
+
+Example:
+
+/* SoC properties */
+
+ mipi_dphy_rx0: mipi-dphy-rx0 {
+ compatible = "rockchip,rk3399-mipi-dphy";
+ clocks = <&cru SCLK_MIPIDPHY_REF>,
+ <&cru SCLK_DPHY_RX0_CFG>,
+ <&cru PCLK_VIO_GRF>;
+ clock-names = "dphy-ref", "dphy-cfg", "grf";
+ power-domains = <&power RK3399_PD_VIO>;
+ bus-width = <4>;
+ };
+
+/* Board properties */
+
+ &mipi_phy_rx0 {
+ ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ port@0 {
+ reg = <0>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ mipi_in_wcam: endpoint@0 {
+ reg = <0>;
+ remote-endpoint = <&wcam_out>;
+ data-lanes = <1 2>;
+ };
+ mipi_in_ucam: endpoint@1 {
+ reg = <1>;
+ remote-endpoint = <&ucam_out>;
+ data-lanes = <1>;
+ };
+ };
+
+ port@1 {
+ reg = <1>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ dphy_rx0_out: endpoint@0 {
+ reg = <0>;
+ remote-endpoint = <&isp0_mipi_in>;
+ };
+ };
+ };
+ };
\ No newline at end of file
--
2.15.0
next prev parent reply other threads:[~2017-11-24 2:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 2:36 [PATCH v2 00/11] Rockchip ISP1 Driver Jacob Chen
2017-11-24 2:36 ` [PATCH v2 01/11] media: videodev2.h, v4l2-ioctl: add rkisp1 meta buffer format Jacob Chen
2017-11-27 10:17 ` Hans Verkuil
2017-11-24 2:36 ` [PATCH v2 02/11] media: rkisp1: Add user space ABI definitions Jacob Chen
2017-11-27 10:26 ` Hans Verkuil
2017-11-28 5:58 ` Jacob Chen
2017-11-24 2:36 ` [PATCH v2 03/11] media: rkisp1: add rockchip isp1 driver Jacob Chen
2017-11-26 17:32 ` kbuild test robot
2017-11-27 11:40 ` Hans Verkuil
2017-11-30 2:51 ` Jacob Chen
2017-11-24 2:36 ` [PATCH v2 04/11] media: rkisp1: add Rockchip MIPI Synopsys DPHY driver Jacob Chen
2017-11-26 17:04 ` kbuild test robot
2017-11-26 18:13 ` kbuild test robot
2017-11-27 12:01 ` Hans Verkuil
2017-11-27 14:15 ` Jose Abreu
2017-11-29 8:38 ` Jacob Chen
2017-11-24 2:37 ` [PATCH v2 05/11] dt-bindings: Document the Rockchip ISP1 bindings Jacob Chen
2017-11-26 22:14 ` Rob Herring
2017-11-24 2:37 ` Jacob Chen [this message]
2017-11-26 22:16 ` [PATCH v2 06/11] dt-bindings: Document the Rockchip MIPI RX D-PHY bindings Rob Herring
2017-11-24 2:37 ` [PATCH v2 07/11] ARM: dts: rockchip: add isp node for rk3288 Jacob Chen
2017-11-24 2:37 ` [PATCH v2 08/11] ARM: dts: rockchip: add rx0 mipi-phy " Jacob Chen
2017-11-24 2:37 ` [PATCH v2 09/11] arm64: dts: rockchip: add isp0 node for rk3399 Jacob Chen
2017-11-24 2:37 ` [PATCH v2 10/11] arm64: dts: rockchip: add rx0 mipi-phy " Jacob Chen
2017-11-24 2:37 ` [PATCH v2 11/11] MAINTAINERS: add entry for Rockchip ISP1 driver Jacob Chen
2017-11-24 6:15 ` [PATCH v2 00/11] Rockchip ISP1 Driver Jacob Chen
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=20171124023706.5702-7-jacob-chen@iotwrt.com \
--to=jacob-chen@iotwrt.com \
--cc=allon.huang@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.cai.linux@gmail.com \
--cc=hans.verkuil@cisco.com \
--cc=heiko@sntech.de \
--cc=jacob2.chen@rock-chips.com \
--cc=jeffy.chen@rock-chips.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@chromium.org \
--cc=zhengsq@rock-chips.com \
--cc=zyc@rock-chips.com \
/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
Powered by JetHome