nvidia,tegra20-usb-phy.txt 3.6 KB

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