xref: /freebsd/sys/contrib/device-tree/Bindings/phy/nvidia,tegra20-usb-phy.txt (revision f81cdf24ba5436367377f7c8e8f51f6df2a75ca7)
1Tegra SOC USB PHY
2
3The device node for Tegra SOC USB PHY:
4
5Required properties :
6 - compatible : For Tegra20, must contain "nvidia,tegra20-usb-phy".
7   For Tegra30, must contain "nvidia,tegra30-usb-phy".  Otherwise, must contain
8   "nvidia,<chip>-usb-phy" plus at least one of the above, where <chip> is
9   tegra114, tegra124, tegra132, or tegra210.
10 - reg : Defines the following set of registers, in the order listed:
11   - The PHY's own register set.
12     Always present.
13   - The register set of the PHY containing the UTMI pad control registers.
14     Present if-and-only-if phy_type == utmi.
15 - phy_type : Should be one of "utmi", "ulpi" or "hsic".
16 - clocks : Defines the clocks listed in the clock-names property.
17 - clock-names : The following clock names must be present:
18   - reg: The clock needed to access the PHY's own registers. This is the
19     associated EHCI controller's clock. Always present.
20   - pll_u: PLL_U. Always present.
21   - timer: The timeout clock (clk_m). Present if phy_type == utmi.
22   - utmi-pads: The clock needed to access the UTMI pad control registers.
23     Present if phy_type == utmi.
24   - ulpi-link: The clock Tegra provides to the ULPI PHY (usually pad DAP_MCLK2
25     with pad group aka "nvidia,pins" cdev2 and pin mux option config aka
26     "nvidia,function" pllp_out4).
27     Present if phy_type == ulpi, and ULPI link mode is in use.
28 - resets : Must contain an entry for each entry in reset-names.
29   See ../reset/reset.txt for details.
30 - reset-names : Must include the following entries:
31   - usb: The PHY's own reset signal.
32   - utmi-pads: The reset of the PHY containing the chip-wide UTMI pad control
33     registers. Required even if phy_type == ulpi.
34
35Required properties for phy_type == ulpi:
36  - nvidia,phy-reset-gpio : The GPIO used to reset the PHY.
37
38Required PHY timing params for utmi phy, for all chips:
39  - nvidia,hssync-start-delay : Number of 480 Mhz clock cycles to wait before
40    start of sync launches RxActive
41  - nvidia,elastic-limit : Variable FIFO Depth of elastic input store
42  - nvidia,idle-wait-delay : Number of 480 Mhz clock cycles of idle to wait
43    before declare IDLE.
44  - nvidia,term-range-adj : Range adjusment on terminations
45  - Either one of the following for HS driver output control:
46    - nvidia,xcvr-setup : integer, uses the provided value.
47    - nvidia,xcvr-setup-use-fuses : boolean, indicates that the value is read
48      from the on-chip fuses
49    If both are provided, nvidia,xcvr-setup-use-fuses takes precedence.
50  - nvidia,xcvr-lsfslew : LS falling slew rate control.
51  - nvidia,xcvr-lsrslew :  LS rising slew rate control.
52
53Required PHY timing params for utmi phy, only on Tegra30 and above:
54  - nvidia,xcvr-hsslew : HS slew rate control.
55  - nvidia,hssquelch-level : HS squelch detector level.
56  - nvidia,hsdiscon-level : HS disconnect detector level.
57
58Optional properties:
59  - nvidia,has-legacy-mode : boolean indicates whether this controller can
60    operate in legacy mode (as APX 2500 / 2600). In legacy mode some
61    registers are accessed through the APB_MISC base address instead of
62    the USB controller.
63  - nvidia,is-wired : boolean. Indicates whether we can do certain kind of power
64    optimizations for the devices that are always connected. e.g. modem.
65  - dr_mode : dual role mode. Indicates the working mode for the PHY. Can be
66    "host", "peripheral", or "otg". Defaults to "host" if not defined.
67      host means this is a host controller
68      peripheral means it is device controller
69      otg means it can operate as either ("on the go")
70  - nvidia,has-utmi-pad-registers : boolean indicates whether this controller
71    contains the UTMI pad control registers common to all USB controllers.
72
73VBUS control (required for dr_mode == otg, optional for dr_mode == host):
74  - vbus-supply: regulator for VBUS
75