From: Krzysztof Witos <kwitos@cadence.com>
Cc: Krzysztof Witos <kwitos@cadence.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"open list:CADENCE MIPI-CSI2 BRIDGES"
<linux-media@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/2] csirx updated doc for csirx with dphy supported
Date: Fri, 8 Jun 2018 11:33:03 +0100 [thread overview]
Message-ID: <20180608103304.16054-2-kwitos@cadence.com> (raw)
In-Reply-To: <20180608103304.16054-1-kwitos@cadence.com>
Signed-off-by: Krzysztof Witos <kwitos@cadence.com>
---
.../devicetree/bindings/media/cdns,csi2rx.txt | 32 +++++++++++++++++++---
1 file changed, 28 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/media/cdns,csi2rx.txt b/Documentation/devicetree/bindings/media/cdns,csi2rx.txt
index 6b02a0657ad9..753b967863c0 100644
--- a/Documentation/devicetree/bindings/media/cdns,csi2rx.txt
+++ b/Documentation/devicetree/bindings/media/cdns,csi2rx.txt
@@ -13,8 +13,7 @@ Required properties:
* p_clk: register bank clock
* pixel_if[0-3]_clk: pixel stream output clock, one for each stream
implemented in hardware, between 0 and 3
-
-Optional properties:
+ * hs_clock: dphy module clock
- phys: phandle to the external D-PHY, phy-names must be provided
- phy-names: must contain "dphy", if the implementation uses an
external D-PHY
@@ -38,18 +37,43 @@ Required subnodes:
in the design.Since there is only one endpoint per port,
the endpoints are not numbered.
+Cadence DPHY
+============
+
+Cadence DPHY block.
+
+Required properties:
+- compatible: should be set to "cdns,dphy".
+- reg: physical base address and length of the DPHY registers.
+- clocks: DPHY reference clocks.
+- clock-names: must contain "psm" and "hs_clk".
+- #phy-cells: must be set to 0.
+
Example:
+dphy1: dphy@fd0d0000 {
+ compatible = "cdns,dphy";
+ reg = <0x0 0xfd0d0000 0x0 0x1000>;
+ clocks = <&dphy_psm_clk>;
+ clock-names = "psm";
+ clock-output-names = "hs_clk";
+ #phy-cells = <0>;
+
csi2rx: csi-bridge@0d060000 {
compatible = "cdns,csi2rx";
reg = <0x0d060000 0x1000>;
clocks = <&byteclock>, <&byteclock>
<&coreclock>, <&coreclock>,
- <&coreclock>, <&coreclock>;
+ <&coreclock>, <&coreclock>,
+ <&dphy_rx_byte_hs_clk>;
clock-names = "sys_clk", "p_clk",
"pixel_if0_clk", "pixel_if1_clk",
- "pixel_if2_clk", "pixel_if3_clk";
+ "pixel_if2_clk", "pixel_if3_clk",
+ "hs_clk";
+
+ phys = <&dphy1>;
+ phy-names = "dphy";
ports {
#address-cells = <1>;
--
2.15.0
next prev parent reply other threads:[~2018-06-08 10:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 10:33 [PATCH 0/2] cadence: csirx: Add Cadence dphy support Krzysztof Witos
2018-06-08 10:33 ` Krzysztof Witos [this message]
2018-06-12 22:02 ` [PATCH 1/2] csirx updated doc for csirx with dphy supported Rob Herring
2018-06-14 6:22 ` Krzysztof Witos
2018-06-12 22:04 ` Rob Herring
2018-06-14 5:57 ` Krzysztof Witos
2018-06-08 10:33 ` [PATCH 2/2] added support for csirx dphy Krzysztof Witos
2018-06-14 7:51 ` Maxime Ripard
2018-06-26 9:04 ` Krzysztof Witos
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=20180608103304.16054-2-kwitos@cadence.com \
--to=kwitos@cadence.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.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).