From: Neil Armstrong <narmstrong@baylibre.com>
To: balbi@kernel.org, gregkh@linuxfoundation.org
Cc: Neil Armstrong <narmstrong@baylibre.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH 2/2] dt-bindings: phy: Add qcom,usb-hsic-phy bindings
Date: Fri, 17 Jun 2016 12:25:19 +0200 [thread overview]
Message-ID: <1466159119-20310-3-git-send-email-narmstrong@baylibre.com> (raw)
In-Reply-To: <1466159119-20310-1-git-send-email-narmstrong@baylibre.com>
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
---
.../devicetree/bindings/phy/qcom,usb-hsic-phy.txt | 95 ++++++++++++++++++++++
1 file changed, 95 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt
diff --git a/Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt b/Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt
new file mode 100644
index 0000000..79259a4
--- /dev/null
+++ b/Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt
@@ -0,0 +1,95 @@
+Qualcomm's MDM9615 USB HISC transceiver controller
+
+- compatible:
+ Usage: required
+ Value type: <string>
+ Definition: Should contain "qcom,usb-hsic-phy".
+
+- reg:
+ Usage: required
+ Value type: <prop-encoded-array>
+ Definition: USB PHY base address and length of the register map
+
+- clocks:
+ Usage: required
+ Value type: <prop-encoded-array>
+ Definition: See clock-bindings.txt section "consumers". List of
+ 5 clock specifiers for interface and core controller
+ clocks.
+
+- clock-names:
+ Usage: required
+ Value type: <string>
+ Definition: Must contain "core", "alt-core", "phy", "cal" and "iface" strings.
+
+- vddcx-supply:
+ Usage: required
+ Value type: <phandle>
+ Definition: phandle to the regulator VDCCX supply node.
+
+- resets:
+ Usage: required
+ Value type: <prop-encoded-array>
+ Definition: See reset.txt section "consumers". PHY reset specifier.
+
+- reset-names:
+ Usage: required
+ Value type: <string>
+ Definition: Must contain "link" string.
+
+- interrupts:
+ Usage: required
+ Value type: <prop-encoded-array>
+ Definition: Interrupt line definition for the PHY
+
+- dr_mode:
+ Usage: required
+ Value type: <prop-encoded-array>
+ Definition: Setup the PHY mode, either "host", "gadget" or "dual"
+
+- qcom,vdd-levels:
+ Usage: required for MDM9615
+ Value type: <prop-encoded-array>
+ Definition: Setup the valid vdd levers for the vddx-supply
+
+- phy_type:
+ Usage: required
+ Value type: <prop-encoded-array>
+ Definition: Shall be "hisc"
+
+- qcom,tlmm:
+ Usage: required for MDM961
+ Value type: <prop-encoded-array>
+ Definition: TLMM syscon phandle to setup the HSIC lines
+
+- qcom,tlmm-cfg:
+ Usage: required for MDM961
+ Value type: <prop-encoded-array>
+ Definition: Shall be two entries of offset, data of the HSIC lines setup
+
+Example:
+ usb_phy: phy@12540000 {
+ compatible = "qcom,usb-hsic-phy";
+ reg = <0x78d9000 0x400>;
+ interrupts = <GIC_SPI 232 IRQ_TYPE_NONE>;
+ dr_mode = "host";
+
+ vddcx-supply = <&pm8018_vdd_dig_corner>;
+
+ clocks = <&gcc USB_HSIC_SYSTEM_CLK>,
+ <&gcc USB_HSIC_XCVR_FS_CLK>,
+ <&gcc USB_HSIC_HSIC_CLK>,
+ <&gcc USB_HSIC_HSIO_CAL_CLK>,
+ <&gcc USB_HSIC_H_CLK>;
+ clock-names = "core", "alt-core", "phy", "cal", "iface";
+
+ resets = <&gcc USB_HSIC_RESET>;
+ reset-names = "link";
+ qcom,vdd-levels = <1 2 4>;
+ phy_type = "hsic";
+
+ qcom,tlmm = <&msmgpio>;
+ qcom,tlmm-cfg = <0x20CC 0x034A4E10
+ 0x20C8 0x034A4E10>;
+ };
+
--
1.9.1
next parent reply other threads:[~2016-06-17 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1466159119-20310-1-git-send-email-narmstrong@baylibre.com>
2016-06-17 10:25 ` Neil Armstrong [this message]
[not found] ` <1466159119-20310-3-git-send-email-narmstrong-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2016-06-20 16:26 ` [PATCH 2/2] dt-bindings: phy: Add qcom,usb-hsic-phy bindings Rob Herring
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=1466159119-20310-3-git-send-email-narmstrong@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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