1*4882a593SmuzhiyunReference code ""drivers/usb/ulpi/omap-ulpi-viewport.c" 2*4882a593Smuzhiyun 3*4882a593SmuzhiyunContains the ulpi read write api's to perform 4*4882a593Smuzhiyunany ulpi phy port access on omap platform. 5*4882a593Smuzhiyun 6*4882a593SmuzhiyunOn omap ehci reg map contains INSNREG05_ULPI 7*4882a593Smuzhiyunregister which offers the ulpi phy access so 8*4882a593Smuzhiyunany ulpi phy commands should be passsed using this 9*4882a593Smuzhiyunregister. 10*4882a593Smuzhiyun 11*4882a593Smuzhiyunomap-ulpi-viewport.c is a low level function 12*4882a593Smuzhiyunimplementation of "drivers/usb/ulpi/ulpi.c" 13*4882a593Smuzhiyun 14*4882a593SmuzhiyunTo enable and use omap-ulpi-viewport.c 15*4882a593Smuzhiyunwe require CONFIG_USB_ULPI_VIEWPORT_OMAP and 16*4882a593SmuzhiyunCONFIG_USB_ULPI be enabled in config file. 17*4882a593Smuzhiyun 18*4882a593SmuzhiyunAny ulpi ops request can be done with ulpi.c 19*4882a593Smuzhiyunand soc specific binding and usage is done with 20*4882a593Smuzhiyunomap-ulpi-viewport implementation. 21*4882a593Smuzhiyun 22*4882a593SmuzhiyunEx: scenario: 23*4882a593Smuzhiyunomap-ehci driver code requests for ulpi phy reset if 24*4882a593Smuzhiyunehci is used in phy mode, which will call ulpi phy reset 25*4882a593Smuzhiyunthe ulpi phy reset does ulpi_read/write from viewport 26*4882a593Smuzhiyunimplementation which will do ulpi reset using the 27*4882a593SmuzhiyunINSNREG05_ULPI register. 28