public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
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,
	Joao.Pinto@synopsys.com, Luis.Oliveira@synopsys.com,
	Jose.Abreu@synopsys.com, Jacob Chen <jacob2.chen@rock-chips.com>
Subject: [PATCH v3 07/12] dt-bindings: Document the Rockchip MIPI RX D-PHY bindings
Date: Wed,  6 Dec 2017 19:19:34 +0800	[thread overview]
Message-ID: <20171206111939.1153-8-jacob-chen@iotwrt.com> (raw)
In-Reply-To: <20171206111939.1153-1-jacob-chen@iotwrt.com>

From: Jacob Chen <jacob2.chen@rock-chips.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          | 71 ++++++++++++++++++++++
 1 file changed, 71 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..cef9450db051
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/rockchip-mipi-dphy.txt
@@ -0,0 +1,71 @@
+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;
+
+Device node example
+-------------------
+
+    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>;
+
+        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

  parent reply	other threads:[~2017-12-06 11:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 11:19 [PATCH v3 00/12] Rockchip ISP1 Driver Jacob Chen
2017-12-06 11:19 ` [PATCH v3 01/12] media: videodev2.h, v4l2-ioctl: add rkisp1 meta buffer format Jacob Chen
2017-12-06 11:19 ` [PATCH v3 02/12] media: doc: add document for " Jacob Chen
2017-12-06 11:19 ` [PATCH v3 03/12] media: rkisp1: Add user space ABI definitions Jacob Chen
2017-12-13 15:34   ` Hans Verkuil
2017-12-06 11:19 ` [PATCH v3 04/12] media: rkisp1: add rockchip isp1 driver Jacob Chen
2017-12-13 16:07   ` Hans Verkuil
2017-12-06 11:19 ` [PATCH v3 05/12] media: rkisp1: add Rockchip MIPI Synopsys DPHY driver Jacob Chen
2017-12-06 11:19 ` [PATCH v3 06/12] dt-bindings: Document the Rockchip ISP1 bindings Jacob Chen
2017-12-07 23:20   ` Rob Herring
2017-12-06 11:19 ` Jacob Chen [this message]
2017-12-07 23:26   ` [PATCH v3 07/12] dt-bindings: Document the Rockchip MIPI RX D-PHY bindings Rob Herring
2017-12-11 16:45   ` Laurent Pinchart
2017-12-18 12:02     ` Jacob Chen
2017-12-06 11:19 ` [PATCH v3 08/12] ARM: dts: rockchip: add isp node for rk3288 Jacob Chen
2017-12-06 11:19 ` [PATCH v3 09/12] ARM: dts: rockchip: add rx0 mipi-phy " Jacob Chen
2017-12-06 11:19 ` [PATCH v3 10/12] arm64: dts: rockchip: add isp0 node for rk3399 Jacob Chen
2017-12-06 11:19 ` [PATCH v3 11/12] arm64: dts: rockchip: add rx0 mipi-phy " Jacob Chen
2017-12-06 11:19 ` [PATCH v3 12/12] MAINTAINERS: add entry for 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=20171206111939.1153-8-jacob-chen@iotwrt.com \
    --to=jacob-chen@iotwrt.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=Jose.Abreu@synopsys.com \
    --cc=Luis.Oliveira@synopsys.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