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