When CONFIG_USB_SUSPEND is enabled, after auto suspend by the usb core driver, USB devices(mouse,keyboard etc.) are not recognised. After auto suspend device state goes to suspend and not resuming to the address. This is fixed by changing the device state to address state on USB cable insertion. Bug 674938 Bug 698734 Change-Id: I837562fd1eb020f400824f2d475289df5fbc1f83 Reviewed-on: http://git-master/r/3494 Reviewed-by: Gary King <gking@nvidia.com> Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
tegra 2 EHCI controllers need transfers aligned to 32B boundaries; enable DMABOUNCE by default whenever USB_TEGRA_HCD is selected, and create DMA pools for the EHCI devices Change-Id: I6c391a52370e19c904cab714a4ebd223c7647329 Reviewed-on: http://git-master.nvidia.com/r/2959 Reviewed-by: Gary King <gking@nvidia.com> Tested-by: Gary King <gking@nvidia.com>
It was observed that when trying to power down the PHY, the RS bit(0:0) in USBCMD register was still set to RUN(1). Calling ehci_halt() before powering down the PHY in tegra_ehci_suspend() to set RS bit to STOP(0) before PHY is powered down. Bug: 695655 Change-Id: I677550be63eebd5140ca466096cb796a21a1167 Reviewed-on: http://git-master/r/2929 Tested-by: Abhishek Aggarwal <aaggarwal@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
Change-Id: I86faa2f56dbfd0ed145f40b04346a85f64bab12c Reviewed-on: http://git-master/r/2508 Reviewed-by: Scott Williams <scwilliams@nvidia.com> Tested-by: Scott Williams <scwilliams@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
When fast wakeup feature is supported by a host controller port, then avoid the restarting of controller. Fast wakeup is enabled on the port where device like usb modem is connected always. BUG 692574: Fast Wakeup for USB modems BUG 594395: Fast Wakeup Change-Id: Iaee9f184189f8a1aa8aa0e440879600c0eb625cc Reviewed-on: http://git-master/r/2375 Tested-by: Seshendra Gadagottu <sgadagottu@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
if the platform data indicates that the controller will be used in OTG mode, do not call request_mem_region since this would conflict with the gadget controller, causing one of the two probes to fail bug 696526 Change-Id: I64f71af8adf7ffa27e98e4fdb42d90de4203efde Reviewed-on: http://git-master/r/2298 Reviewed-by: Venkata (Muni) Anda <vanda@nvidia.com> Tested-by: Venkata (Muni) Anda <vanda@nvidia.com> Tested-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com> Reviewed-by: Abhishek Aggarwal <aaggarwal@nvidia.com> Tested-by: Abhishek Aggarwal <aaggarwal@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
The USB device connected to USB1(OTG) port was not getting detected at boot time. Reason being that on phy power down (host mode), there was some delay in VBUS getting disabled. Because of this the OTG state was getting set to "peripheral" instead of "host". Fixed this by waiting for VBUS to be disabled in phy power down with a max wait time of phy hardware time out (1 sec). Change-Id: I78e561e28d942fa9931dfb88656281b02264859f Reviewed-on: http://git-master/r/1837 Reviewed-by: Gary King <gking@nvidia.com> Tested-by: Gary King <gking@nvidia.com>
Change-Id: I0bac36fe5ad4ec94b0b6fc6608083a84bcb2672e
some EHCI-compliant host controllers, like Tegra, support dual-mode device & host operation; add an otg_transceiver structure to the EHCI HCD to support this mode of operation Change-Id: I6722e036cad06a6eee3bf89b6ba4c88928eafca4
only reset the controller when doing so won't also reset the phy (Tegra quirk) Change-Id: I549a18977d0d5ebfa12c32016aa9e6bffaa8643c