1*c66ec88fSEmmanuel VadotOMAP HS USB EHCI controller 2*c66ec88fSEmmanuel Vadot 3*c66ec88fSEmmanuel VadotThis device is usually the child of the omap-usb-host 4*c66ec88fSEmmanuel VadotDocumentation/devicetree/bindings/mfd/omap-usb-host.txt 5*c66ec88fSEmmanuel Vadot 6*c66ec88fSEmmanuel VadotRequired properties: 7*c66ec88fSEmmanuel Vadot 8*c66ec88fSEmmanuel Vadot- compatible: should be "ti,ehci-omap" 9*c66ec88fSEmmanuel Vadot- reg: should contain one register range i.e. start and length 10*c66ec88fSEmmanuel Vadot- interrupts: description of the interrupt line 11*c66ec88fSEmmanuel Vadot 12*c66ec88fSEmmanuel VadotOptional properties: 13*c66ec88fSEmmanuel Vadot 14*c66ec88fSEmmanuel Vadot- phys: list of phandles to PHY nodes. 15*c66ec88fSEmmanuel Vadot This property is required if at least one of the ports are in 16*c66ec88fSEmmanuel Vadot PHY mode i.e. OMAP_EHCI_PORT_MODE_PHY 17*c66ec88fSEmmanuel Vadot 18*c66ec88fSEmmanuel VadotTo specify the port mode, see 19*c66ec88fSEmmanuel VadotDocumentation/devicetree/bindings/mfd/omap-usb-host.txt 20*c66ec88fSEmmanuel Vadot 21*c66ec88fSEmmanuel VadotExample for OMAP4: 22*c66ec88fSEmmanuel Vadot 23*c66ec88fSEmmanuel Vadotusbhsehci: ehci@4a064c00 { 24*c66ec88fSEmmanuel Vadot compatible = "ti,ehci-omap"; 25*c66ec88fSEmmanuel Vadot reg = <0x4a064c00 0x400>; 26*c66ec88fSEmmanuel Vadot interrupts = <0 77 0x4>; 27*c66ec88fSEmmanuel Vadot}; 28*c66ec88fSEmmanuel Vadot 29*c66ec88fSEmmanuel Vadot&usbhsehci { 30*c66ec88fSEmmanuel Vadot phys = <&hsusb1_phy 0 &hsusb3_phy>; 31*c66ec88fSEmmanuel Vadot}; 32