1 Device tree binding for NVIDIA Tegra XUSB pad controller
2 ========================================================
4 The Tegra XUSB pad controller manages a set of I/O lanes (with differential
5 signals) which connect directly to pins/pads on the SoC package. Each lane
6 is controlled by a HW block referred to as a "pad" in the Tegra hardware
7 documentation. Each such "pad" may control either one or multiple lanes,
8 and thus contains any logic common to all its lanes. Each lane can be
9 separately configured and powered up.
11 Some of the lanes are high-speed lanes, which can be used for PCIe, SATA or
12 super-speed USB. Other lanes are for various types of low-speed, full-speed
13 or high-speed USB (such as UTMI, ULPI and HSIC). The XUSB pad controller
14 contains a software-configurable mux that sits between the I/O controller
15 ports (e.g. PCIe) and the lanes.
17 In addition to per-lane configuration, USB 3.0 ports may require additional
18 settings on a per-board basis.
20 Pads will be represented as children of the top-level XUSB pad controller
21 device tree node. Each lane exposed by the pad will be represented by its
22 own subnode and can be referenced by users of the lane using the standard
23 PHY bindings, as described by the phy-bindings.txt file in this directory.
25 The Tegra hardware documentation refers to the connection between the XUSB
26 pad controller and the XUSB controller as "ports". This is confusing since
27 "port" is typically used to denote the physical USB receptacle. The device
28 tree binding in this document uses the term "port" to refer to the logical
29 abstraction of the signals that are routed to a USB receptacle (i.e. a PHY
30 for the USB signal, the VBUS power supply, the USB 2.0 companion port for
31 USB 3.0 receptacles, ...).
35 - compatible: Must be:
36 - Tegra124: "nvidia,tegra124-xusb-padctl"
37 - Tegra132: "nvidia,tegra132-xusb-padctl", "nvidia,tegra124-xusb-padctl"
38 - Tegra210: "nvidia,tegra210-xusb-padctl"
39 - Tegra186: "nvidia,tegra186-xusb-padctl"
40 - reg: Physical base address and length of the controller's registers.
41 - resets: Must contain an entry for each entry in reset-names.
42 - reset-names: Must include the following entries:
46 - avdd-pll-utmip-supply: UTMI PLL power supply. Must supply 1.8 V.
47 - avdd-pll-erefe-supply: PLLE reference PLL power supply. Must supply 1.05 V.
48 - avdd-pex-pll-supply: PCIe/USB3 PLL power supply. Must supply 1.05 V.
49 - hvdd-pex-pll-e-supply: High-voltage PLLE power supply. Must supply 3.3 V.
52 - avdd-pll-utmip-supply: UTMI PLL power supply. Must supply 1.8 V.
53 - avdd-pll-uerefe-supply: PLLE reference PLL power supply. Must supply 1.05 V.
54 - dvdd-pex-pll-supply: PCIe/USB3 PLL power supply. Must supply 1.05 V.
55 - hvdd-pex-pll-e-supply: High-voltage PLLE power supply. Must supply 1.8 V.
58 - avdd-pll-erefeut-supply: UPHY brick and reference clock as well as UTMI PHY
59 power supply. Must supply 1.8 V.
60 - avdd-usb-supply: USB I/Os, VBUS, ID, REXT, D+/D- power supply. Must supply
62 - vclamp-usb-supply: Bias rail for USB pad. Must supply 1.8 V.
63 - vddio-hsic-supply: HSIC PHY power supply. Must supply 1.2 V.
69 A required child node named "pads" contains a list of subnodes, one for each
70 of the pads exposed by the XUSB pad controller. Each pad may need additional
71 resources that can be referenced in its pad node.
73 The "status" property is used to enable or disable the use of a pad. If set
74 to "disabled", the pad will not be used on the given board. In order to use
75 the pad and any of its lanes, this property must be set to "okay".
77 For Tegra124 and Tegra132, the following pads exist: usb2, ulpi, hsic, pcie
78 and sata. No extra resources are required for operation of these pads.
80 For Tegra210, the following pads exist: usb2, hsic, pcie and sata. Below is
81 a description of the properties of each pad.
87 - clocks: Must contain an entry for each entry in clock-names.
88 - clock-names: Must contain the following entries:
89 - "trk": phandle and specifier referring to the USB2 tracking clock
95 - clocks: Must contain an entry for each entry in clock-names.
96 - clock-names: Must contain the following entries:
97 - "trk": phandle and specifier referring to the HSIC tracking clock
103 - clocks: Must contain an entry for each entry in clock-names.
104 - clock-names: Must contain the following entries:
105 - "pll": phandle and specifier referring to the PLLE
106 - resets: Must contain an entry for each entry in reset-names.
107 - reset-names: Must contain the following entries:
108 - "phy": reset for the PCIe UPHY block
114 - resets: Must contain an entry for each entry in reset-names.
115 - reset-names: Must contain the following entries:
116 - "phy": reset for the SATA UPHY block
122 Each pad node has a child named "lanes" that contains one or more children of
123 its own, each representing one of the lanes controlled by the pad.
127 - status: Defines the operation status of the PHY. Valid values are:
128 - "disabled": the PHY is disabled
129 - "okay": the PHY is enabled
130 - #phy-cells: Should be 0. Since each lane represents a single PHY, there is
131 no need for an additional specifier.
132 - nvidia,function: The output function of the PHY. See below for a list of
133 valid functions per SoC generation.
135 For Tegra124 and Tegra132, the list of valid PHY nodes is given below:
136 - usb2: usb2-0, usb2-1, usb2-2
137 - functions: "snps", "xusb", "uart"
139 - functions: "snps", "xusb"
140 - hsic: hsic-0, hsic-1
141 - functions: "snps", "xusb"
142 - pcie: pcie-0, pcie-1, pcie-2, pcie-3, pcie-4
143 - functions: "pcie", "usb3-ss"
145 - functions: "usb3-ss", "sata"
147 For Tegra210, the list of valid PHY nodes is given below:
148 - usb2: usb2-0, usb2-1, usb2-2, usb2-3
149 - functions: "snps", "xusb", "uart"
150 - hsic: hsic-0, hsic-1
151 - functions: "snps", "xusb"
152 - pcie: pcie-0, pcie-1, pcie-2, pcie-3, pcie-4, pcie-5, pcie-6
153 - functions: "pcie-x1", "usb3-ss", "pcie-x4"
155 - functions: "usb3-ss", "sata"
161 A required child node named "ports" contains a list of all the ports exposed
162 by the XUSB pad controller. Per-port configuration is only required for USB.
168 - status: Defines the operation status of the port. Valid values are:
169 - "disabled": the port is disabled
170 - "okay": the port is enabled
171 - mode: A string that determines the mode in which to run the port. Valid
173 - "host": for USB host mode
174 - "device": for USB device mode
175 - "otg": for USB OTG mode
178 - nvidia,internal: A boolean property whose presence determines that a port
179 is internal. In the absence of this property the port is considered to be
181 - vbus-supply: phandle to a regulator supplying the VBUS voltage.
187 - status: Defines the operation status of the port. Valid values are:
188 - "disabled": the port is disabled
189 - "okay": the port is enabled
190 - nvidia,internal: A boolean property whose presence determines that a port
191 is internal. In the absence of this property the port is considered to be
193 - vbus-supply: phandle to a regulator supplying the VBUS voltage.
199 - status: Defines the operation status of the port. Valid values are:
200 - "disabled": the port is disabled
201 - "okay": the port is enabled
204 - vbus-supply: phandle to a regulator supplying the VBUS voltage.
206 Super-speed USB ports:
207 ----------------------
210 - status: Defines the operation status of the port. Valid values are:
211 - "disabled": the port is disabled
212 - "okay": the port is enabled
213 - nvidia,usb2-companion: A single cell that specifies the physical port number
214 to map this super-speed USB port to. The range of valid port numbers varies
215 with the SoC generation:
216 - 0-2: for Tegra124 and Tegra132
220 - nvidia,internal: A boolean property whose presence determines that a port
221 is internal. In the absence of this property the port is considered to be
224 For Tegra124 and Tegra132, the XUSB pad controller exposes the following
226 - 3x USB2: usb2-0, usb2-1, usb2-2
228 - 2x HSIC: hsic-0, hsic-1
229 - 2x super-speed USB: usb3-0, usb3-1
231 For Tegra210, the XUSB pad controller exposes the following ports:
232 - 4x USB2: usb2-0, usb2-1, usb2-2, usb2-3
233 - 2x HSIC: hsic-0, hsic-1
234 - 4x super-speed USB: usb3-0, usb3-1, usb3-2, usb3-3
240 Tegra124 and Tegra132:
241 ----------------------
247 compatible = "nvidia,tegra124-xusb-padctl";
249 compatible = "nvidia,tegra132-xusb-padctl",
250 "nvidia,tegra124-xusb-padctl";
251 reg = <0x0 0x7009f000 0x0 0x1000>;
252 resets = <&tegra_car 142>;
253 reset-names = "padctl";
393 nvidia,function = "xusb";
398 nvidia,function = "xusb";
403 nvidia,function = "xusb";
414 nvidia,function = "usb3-ss";
419 nvidia,function = "pcie";
424 nvidia,function = "pcie";
435 nvidia,function = "sata";
460 vbus-supply = <&vdd_usb3_vbus>;
476 compatible = "nvidia,tegra210-xusb-padctl";
477 reg = <0x0 0x7009f000 0x0 0x1000>;
478 resets = <&tegra_car 142>;
479 reset-names = "padctl";
485 clocks = <&tegra_car TEGRA210_CLK_USB2_TRK>;
513 clocks = <&tegra_car TEGRA210_CLK_HSIC_TRK>;
531 clocks = <&tegra_car TEGRA210_CLK_PLL_E>;
533 resets = <&tegra_car 205>;
576 clocks = <&tegra_car TEGRA210_CLK_PLL_E>;
578 resets = <&tegra_car 204>;
645 nvidia,function = "xusb";
650 nvidia,function = "xusb";
655 nvidia,function = "xusb";
660 nvidia,function = "xusb";
671 nvidia,function = "pcie-x1";
676 nvidia,function = "pcie-x4";
681 nvidia,function = "pcie-x4";
686 nvidia,function = "pcie-x4";
691 nvidia,function = "pcie-x4";
696 nvidia,function = "usb3-ss";
701 nvidia,function = "usb3-ss";
712 nvidia,function = "sata";
727 vbus-supply = <&vdd_5v0_rtl>;
733 vbus-supply = <&vdd_usb_vbus>;
744 nvidia,lanes = "pcie-6";
750 nvidia,lanes = "pcie-5";