linux-toradex.git/drivers/usb, branch tegra-10.9.9 Linux kernel for Apalis and Colibri modules [[ARM/Tegra] Clean up build warning message 2010-10-27T22:08:28+00:00 lazhao lazhao@nvidia.com 2010-10-16T02:38:49+00:00 6c61a8a4857a7b3740865a4a334604fb4bf44eed Clean up warning message caused by unused variable and improper struct type. Bug 682070 Change-Id: I3409ad22e67252df14d6d14898aa8792a0019574 Reviewed-on: http://git-master/r/8436 Reviewed-by: Lance Zhao <lazhao@nvidia.com> Tested-by: Lance Zhao <lazhao@nvidia.com> Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com> Reviewed-by: Varun Colbert <vcolbert@nvidia.com> Tested-by: Varun Colbert <vcolbert@nvidia.com> 
Clean up warning message caused by unused variable and
improper struct type.

Bug 682070

Change-Id: I3409ad22e67252df14d6d14898aa8792a0019574
Reviewed-on: http://git-master/r/8436
Reviewed-by: Lance Zhao <lazhao@nvidia.com>
Tested-by: Lance Zhao <lazhao@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
[ehci-tegra] Fix VBUS handling in OTG mode 2010-10-21T22:35:15+00:00 Venkat Moganty vmoganty@nvidia.com 2010-10-20T06:34:49+00:00 cb800e32170138f00aad5b724dc56c18ce1b07ad When USB cable is removed from the USB1 port side then VBUS is turned off but, if USB cable is removed from the device side then VBUS is not getting turned off and is showing high even when USB cable is removed completely from the USB1 port. Fixed this by checking the OTG state "OTG_STATE_A_SUSPEND" and then turning off the VBUS and phy power down. Bug 741587 Change-Id: Ib8f3dbddc48de0d12179dbd504503621854f44cd Reviewed-on: http://git-master/r/8199 Reviewed-by: Lance Zhao <lazhao@nvidia.com> Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com> Tested-by: Lance Zhao <lazhao@nvidia.com> Reviewed-by: Varun Colbert <vcolbert@nvidia.com> Tested-by: Varun Colbert <vcolbert@nvidia.com> 
When USB cable is removed from the USB1 port side then VBUS is turned
off but, if USB cable is removed from the device side then VBUS is not
getting turned off and is showing high even when USB cable is removed
completely from the USB1 port. Fixed this by checking the OTG state
"OTG_STATE_A_SUSPEND" and then turning off the VBUS and phy power down.

Bug 741587

Change-Id: Ib8f3dbddc48de0d12179dbd504503621854f44cd
Reviewed-on: http://git-master/r/8199
Reviewed-by: Lance Zhao <lazhao@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
Tested-by: Lance Zhao <lazhao@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
[tegra] huawei EM770 modem support 2010-10-15T03:28:24+00:00 Rakesh Kumar krakesh@nvidia.com 2010-10-14T04:53:34+00:00 7e5e54136472ab0170eeb5d9c1992ffed9bb0920 Added EM770 vendor and product id in usb serial driver. Bug 721467 Change-Id: Ib64820f25b02a69c8a366b9251f9419dd4bfa786 Reviewed-on: http://git-master.nvidia.com/r/8385 Reviewed-by: Rakesh Kumar <krakesh@nvidia.com> Tested-by: Rakesh Kumar <krakesh@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-by: Varun Colbert <vcolbert@nvidia.com> Tested-by: Varun Colbert <vcolbert@nvidia.com> 
Added EM770 vendor and product id in usb serial driver.

Bug 721467

Change-Id: Ib64820f25b02a69c8a366b9251f9419dd4bfa786
Reviewed-on: http://git-master.nvidia.com/r/8385
Reviewed-by: Rakesh Kumar <krakesh@nvidia.com>
Tested-by: Rakesh Kumar <krakesh@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
[tegra-ehci]USB device detection for host mode in LP0 2010-10-06T05:16:52+00:00 Venkat Moganty vmoganty@nvidia.com 2010-09-28T16:02:08+00:00 8eaa0afc05248d324ec8d46a557740a043d8e641 USB devices are not recognised when connected to the USB port, when system is already in LP0. Root port power is not getting enabled when resume from LP0. By the time root hub checks for the port connection auto suspend is getting called and device is not recognised. Fixed this by enabling the root port power during the ehci_restart functionality. Bug 741890 (cherry picked from commit 188bf7050751a40d6f2d6a858e2702774fc70f77) Change-Id: Ib88ed3fc4b01719777a0e49e27434ef6425bc53d Reviewed-on: http://git-master/r/7834 Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com> Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com> Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com> 
USB devices are not recognised when connected to the USB port, when system is
already in LP0. Root port power is not getting enabled when resume from LP0.
By the time root hub checks for the port connection auto suspend is getting
called and device is not recognised. Fixed this by enabling the root port power
during the ehci_restart functionality.

Bug 741890

(cherry picked from commit 188bf7050751a40d6f2d6a858e2702774fc70f77)

Change-Id: Ib88ed3fc4b01719777a0e49e27434ef6425bc53d
Reviewed-on: http://git-master/r/7834
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
[usb-host]Remove controller restart in host mode during resume 2010-10-05T21:51:10+00:00 Venkat Moganty vmoganty@nvidia.com 2010-09-05T01:46:46+00:00 f53faa616294450f1ed05b5bfd249b577b709399 During resume from LP0 controller is getting restarted in host mode due to this hcd state is getting changed from the suspend state. Controller state should not be changed for host mode. Fixed this to restart the controller only in OTG mode. Bug 724437 (cherry picked from commit cbea530301ae3d9a4a7271d11c819bfc8de8f892) Change-Id: Idc2897a2790087e00ee66e30fea734c9d117029e Reviewed-on: http://git-master/r/7833 Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com> Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com> Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com> 
During resume from LP0 controller is getting restarted in host mode due to this
hcd state is getting changed from the suspend state. Controller state should not
be changed for host mode. Fixed this to restart the controller only in OTG mode.

Bug 724437

(cherry picked from commit cbea530301ae3d9a4a7271d11c819bfc8de8f892)

Change-Id: Idc2897a2790087e00ee66e30fea734c9d117029e
Reviewed-on: http://git-master/r/7833
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
[usb-hcd]Adding missed memory barrier in the hcd driver 2010-10-05T21:49:18+00:00 Venkat Moganty vmoganty@nvidia.com 2010-09-23T17:44:57+00:00 80833ca384f1a58a207f98bba66905c6e0caac97 There is one wmb missing in the usb host controller driver after the queue head update. Due to this data transaction is not happening on the bus after urb submission by the hcd driver. Register updates/queue heads data in the memory is not reflected on the AHB bus. After adding the wmb after queue head update data transaction the USB bus started with out any delay. Bug 737242 (cherry picked from commit eff18c3f40253f7af0b576126b954d8572cbea64) Change-Id: I9f3ae6d8743a03a58034a82f4fe2850fd7278c4f Reviewed-on: http://git-master/r/7747 Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com> Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com> Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com> 
There is one wmb missing in the usb host controller driver after the queue head
update. Due to this data transaction is not happening on the bus after urb
submission by the hcd driver. Register updates/queue heads data in the memory
is not reflected on the AHB bus. After adding the wmb after queue head update
data transaction the USB bus started with out any delay.

Bug 737242

(cherry picked from commit eff18c3f40253f7af0b576126b954d8572cbea64)

Change-Id: I9f3ae6d8743a03a58034a82f4fe2850fd7278c4f
Reviewed-on: http://git-master/r/7747
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
[tegra-udc] Fix device compliance test 2010-10-01T06:23:13+00:00 Rama Kandhala rkandhala@nvidia.com 2010-09-28T09:33:03+00:00 b50b242037add491f8ccc2859c4e0ed3cd7468f6 On k32, remote wake up is enabled in the descriptor based on gadget->ops. Since, remote wakeup is not supported, disabled gadget->op->remote_wakeup based on USB_ANDROID. Bug 710624 (cherry picked from commit c0340053278c9c9ceb98772cc3566d298dca4d9a) Change-Id: I760632dd38a9f56dadfbb4d446e83f28cdb5338f Reviewed-on: http://git-master/r/7556 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com> Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com> 
On k32, remote wake up is enabled in the descriptor based on gadget->ops. Since,
remote wakeup is not supported, disabled gadget->op->remote_wakeup based
on USB_ANDROID.

Bug 710624

(cherry picked from commit c0340053278c9c9ceb98772cc3566d298dca4d9a)

Change-Id: I760632dd38a9f56dadfbb4d446e83f28cdb5338f
Reviewed-on: http://git-master/r/7556
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
[USB ADB]: rate control adb prints 2010-09-21T18:12:41+00:00 Narendra Damahe ndamahe@nvidia.com 2010-09-17T20:40:52+00:00 3dab0e0518e951e62ebcdceb9f170f304cb9d9b5 limit the number of times adb_open and adb_release may be printed in a short period of time, to prevent adb death spirals when exiting suspend (cherry picked from commit 3a1e33f6715f7133ba9fe26d68342c1ff6106b20) Change-Id: I575f38269c9a4c46a3a59ff7a06c8bda36a0c0d4 Reviewed-on: http://git-master/r/6723 Reviewed-by: Narendra Damahe <ndamahe@nvidia.com> Tested-by: Narendra Damahe <ndamahe@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
limit the number of times adb_open and adb_release may be printed
in a short period of time, to prevent adb death spirals when
exiting suspend

(cherry picked from commit 3a1e33f6715f7133ba9fe26d68342c1ff6106b20)

Change-Id: I575f38269c9a4c46a3a59ff7a06c8bda36a0c0d4
Reviewed-on: http://git-master/r/6723
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
[usb-msd]Fix to increase MSD write performance 2010-09-09T16:49:59+00:00 Venkat Moganty vmoganty@nvidia.com 2010-09-05T19:59:15+00:00 9053084636be53fab6c0d9f80863b890e981096a MSD write performance is decreased due to the file_sync() called in the write path this is introduced in the K32. After removing this write performance is increased and it is back to K29. Bug 727609 (cherry picked from commit 3674a60b8d4ede5d9305bf59a205e9f16e025f2a) Change-Id: I99e63302e1b189b600163c216847eae437e86a9f Reviewed-on: http://git-master/r/6246 Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com> Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com> Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com> 
MSD write performance is decreased due to the file_sync() called in the write
path this is introduced in the K32. After removing this write performance is
increased and it is back to K29.

Bug 727609

(cherry picked from commit 3674a60b8d4ede5d9305bf59a205e9f16e025f2a)

Change-Id: I99e63302e1b189b600163c216847eae437e86a9f
Reviewed-on: http://git-master/r/6246
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
[tegra-ehci] Fix Usb device detection for config USB_SUSPEND 2010-08-24T23:53:56+00:00 Venkat Moganty vmoganty@nvidia.com 2010-08-12T11:38:14+00:00 04dbd92636bdf1e4652d00d03c7a5a6ebbad8a4c When CONFIG_USB_SUSPEND is enabled USB device detection is not working. This is due to the wrong API called to resume the hub and HUB resume funtionality not happening properly. Fixed this by calling the correct API to resume the HUB driver when auto suspend is called. Bug 713237 Bug 713966 Change-Id: Ia4d091fd29ea7ebfe5844cf5685fc5a86e66d12a Reviewed-on: http://git-master/r/4984 Reviewed-by: Abhishek Aggarwal <aaggarwal@nvidia.com> Tested-by: Abhishek Aggarwal <aaggarwal@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
When CONFIG_USB_SUSPEND is enabled USB device detection is not working. This is
due to the wrong API called to resume the hub and HUB resume funtionality not
happening properly. Fixed this by calling the correct API to resume the HUB
driver when auto suspend is called.

Bug 713237
Bug 713966

Change-Id: Ia4d091fd29ea7ebfe5844cf5685fc5a86e66d12a
Reviewed-on: http://git-master/r/4984
Reviewed-by: Abhishek Aggarwal <aaggarwal@nvidia.com>
Tested-by: Abhishek Aggarwal <aaggarwal@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>