omap-usb.txt 2.6 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980
  1. OMAP GLUE AND OTHER OMAP SPECIFIC COMPONENTS
  2. OMAP MUSB GLUE
  3. - compatible : Should be "ti,omap4-musb" or "ti,omap3-musb"
  4. - ti,hwmods : must be "usb_otg_hs"
  5. - multipoint : Should be "1" indicating the musb controller supports
  6. multipoint. This is a MUSB configuration-specific setting.
  7. - num-eps : Specifies the number of endpoints. This is also a
  8. MUSB configuration-specific setting. Should be set to "16"
  9. - ram-bits : Specifies the ram address size. Should be set to "12"
  10. - interface-type : This is a board specific setting to describe the type of
  11. interface between the controller and the phy. It should be "0" or "1"
  12. specifying ULPI and UTMI respectively.
  13. - mode : Should be "3" to represent OTG. "1" signifies HOST and "2"
  14. represents PERIPHERAL.
  15. - power : Should be "50". This signifies the controller can supply up to
  16. 100mA when operating in host mode.
  17. - usb-phy : the phandle for the PHY device
  18. - phys : the phandle for the PHY device (used by generic PHY framework)
  19. - phy-names : the names of the PHY corresponding to the PHYs present in the
  20. *phy* phandle.
  21. Optional properties:
  22. - ctrl-module : phandle of the control module this glue uses to write to
  23. mailbox
  24. SOC specific device node entry
  25. usb_otg_hs: usb_otg_hs@4a0ab000 {
  26. compatible = "ti,omap4-musb";
  27. ti,hwmods = "usb_otg_hs";
  28. multipoint = <1>;
  29. num-eps = <16>;
  30. ram-bits = <12>;
  31. ctrl-module = <&omap_control_usb>;
  32. phys = <&usb2_phy>;
  33. phy-names = "usb2-phy";
  34. };
  35. Board specific device node entry
  36. &usb_otg_hs {
  37. interface-type = <1>;
  38. mode = <3>;
  39. power = <50>;
  40. };
  41. OMAP DWC3 GLUE
  42. - compatible : Should be
  43. * "ti,dwc3" for OMAP5 and DRA7
  44. * "ti,am437x-dwc3" for AM437x
  45. - ti,hwmods : Should be "usb_otg_ss"
  46. - reg : Address and length of the register set for the device.
  47. - interrupts : The irq number of this device that is used to interrupt the
  48. MPU
  49. - #address-cells, #size-cells : Must be present if the device has sub-nodes
  50. - utmi-mode : controls the source of UTMI/PIPE status for VBUS and OTG ID.
  51. It should be set to "1" for HW mode and "2" for SW mode.
  52. - ranges: the child address space are mapped 1:1 onto the parent address space
  53. Optional Properties:
  54. - extcon : phandle for the extcon device omap dwc3 uses to detect
  55. connect/disconnect events.
  56. - vbus-supply : phandle to the regulator device tree node if needed.
  57. Sub-nodes:
  58. The dwc3 core should be added as subnode to omap dwc3 glue.
  59. - dwc3 :
  60. The binding details of dwc3 can be found in:
  61. Documentation/devicetree/bindings/usb/dwc3.txt
  62. omap_dwc3 {
  63. compatible = "ti,dwc3";
  64. ti,hwmods = "usb_otg_ss";
  65. reg = <0x4a020000 0x1ff>;
  66. interrupts = <0 93 4>;
  67. #address-cells = <1>;
  68. #size-cells = <1>;
  69. utmi-mode = <2>;
  70. ranges;
  71. };