Merge tag 'v4.11-rc5' into next
[sfrench/cifs-2.6.git] / Documentation / devicetree / bindings / phy / qcom,usb-hs-phy.txt
1 Qualcomm's USB HS PHY
2
3 PROPERTIES
4
5 - compatible:
6     Usage: required
7     Value type: <string>
8     Definition: Should contain "qcom,usb-hs-phy" and more specifically one of the
9                 following:
10
11                         "qcom,usb-hs-phy-apq8064"
12                         "qcom,usb-hs-phy-msm8916"
13                         "qcom,usb-hs-phy-msm8974"
14
15 - #phy-cells:
16     Usage: required
17     Value type: <u32>
18     Definition: Should contain 0
19
20 - clocks:
21     Usage: required
22     Value type: <prop-encoded-array>
23     Definition: Should contain clock specifier for the reference and sleep
24                 clocks
25
26 - clock-names:
27     Usage: required
28     Value type: <stringlist>
29     Definition: Should contain "ref" and "sleep" for the reference and sleep
30                 clocks respectively
31
32 - resets:
33     Usage: required
34     Value type: <prop-encoded-array>
35     Definition: Should contain the phy and POR resets
36
37 - reset-names:
38     Usage: required
39     Value type: <stringlist>
40     Definition: Should contain "phy" and "por" for the phy and POR resets
41                 respectively
42
43 - v3p3-supply:
44     Usage: required
45     Value type: <phandle>
46     Definition: Should contain a reference to the 3.3V supply
47
48 - v1p8-supply:
49     Usage: required
50     Value type: <phandle>
51     Definition: Should contain a reference to the 1.8V supply
52
53 - extcon:
54     Usage: optional
55     Value type: <prop-encoded-array>
56     Definition: Should contain the vbus extcon
57
58 - qcom,init-seq:
59     Usage: optional
60     Value type: <u8 array>
61     Definition: Should contain a sequence of ULPI address and value pairs to
62                 program into the ULPI_EXT_VENDOR_SPECIFIC area. This is related
63                 to Device Mode Eye Diagram test. The addresses are offsets
64                 from the ULPI_EXT_VENDOR_SPECIFIC address, for example,
65                 <0x1 0x53> would mean "write the value 0x53 to address 0x81".
66
67 EXAMPLE
68
69 otg: usb-controller {
70         ulpi {
71                 phy {
72                         compatible = "qcom,usb-hs-phy-msm8974", "qcom,usb-hs-phy";
73                         #phy-cells = <0>;
74                         clocks = <&xo_board>, <&gcc GCC_USB2A_PHY_SLEEP_CLK>;
75                         clock-names = "ref", "sleep";
76                         resets = <&gcc GCC_USB2A_PHY_BCR>, <&otg 0>;
77                         reset-names = "phy", "por";
78                         v3p3-supply = <&pm8941_l24>;
79                         v1p8-supply = <&pm8941_l6>;
80                         extcon = <&smbb>;
81                         qcom,init-seq = /bits/ 8 <0x1 0x63>;
82                 };
83         };
84 };