From: Alan Douglas <adouglas@cadence.com>
To: <kishon@ti.com>, <linux-kernel@vger.kernel.org>
Cc: <stelford@cadence.com>, Alan Douglas <adouglas@cadence.com>
Subject: [RFC PATCH 1/2] dt-bindings: phy: Document cadence Sierra PHY bindings
Date: Fri, 17 Aug 2018 13:31:20 +0100 [thread overview]
Message-ID: <1534509080-12821-1-git-send-email-adouglas@cadence.com> (raw)
Add DT binding documentation for Sierra PHY. The PHY supports
a number of different protocols, including PCIe and USB. The
number of lanes can also be configured.
Signed-off-by: Alan Douglas <adouglas@cadence.com>
---
.../devicetree/bindings/phy/cdns-sierra-phy.txt | 29 ++++++++++++++++++++++
1 file changed, 29 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/cdns-sierra-phy.txt
diff --git a/Documentation/devicetree/bindings/phy/cdns-sierra-phy.txt b/Documentation/devicetree/bindings/phy/cdns-sierra-phy.txt
new file mode 100644
index 0000000..846bdfc
--- /dev/null
+++ b/Documentation/devicetree/bindings/phy/cdns-sierra-phy.txt
@@ -0,0 +1,29 @@
+Cadence Sierra PHY
+-----------------------
+
+Required properties:
+ - compatible: cdns,sierra-phy
+ - clocks: Must contain an entry in clock-names.
+ See ../clocks/clock-bindings.txt for details.
+ - clock-names: Must be "phy_clk"
+ - resets: Must contain an entry for each in reset-names.
+ See ../reset/reset.txt for details.
+ - reset-names: Must include "sierra_reset" and "sierra_apb"
+ "sierra_reset" must control the reset line to the PHY
+ "sierra_apb" must control the reset line to the APB PHY interface
+ - #phy-cells: must be 2
+ - reg : register range for the PHY
+ - reg-names: Must be "reg"
+
+
+Example:
+ pcie_phy4: pcie-phy4@fd240000 {
+ compatible = "cdns,sierra-phy";
+ reg = <0x0 0xfd240000 0x0 0x40000>;
+ reg-names = "reg";
+ #phy-cells = <2>;
+ resets = <&dummyrst2 0>, <&dummyrst3 0>;
+ reset-names = "sierra_reset","sierra_apb";
+ clocks = <&phyclock>;
+ clock-names = "phy_clk";
+ };
--
1.9.0
reply other threads:[~2018-08-17 12:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1534509080-12821-1-git-send-email-adouglas@cadence.com \
--to=adouglas@cadence.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stelford@cadence.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;
as well as URLs for NNTP newsgroup(s).