linux-toradex.git, branch tegra-9.12.12 Linux kernel for Apalis and Colibri modules tegra: added delay to avoid hang after Lp0 resume 2010-05-21T01:31:19+00:00 Narendra Damahe ndamahe@nvidia.com 2010-05-20T23:12:53+00:00 7293fee7358786224051182853c8200388b838c7 Bug 679959 Change-Id: Id541c2f51fe2e0cb2c4cbb08aafbcb53da251218 Reviewed-on: http://git-master/r/1468 Reviewed-by: Narendra Damahe <ndamahe@nvidia.com> Tested-by: Narendra Damahe <ndamahe@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
Bug 679959

Change-Id: Id541c2f51fe2e0cb2c4cbb08aafbcb53da251218
Reviewed-on: http://git-master/r/1468
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
tegra:adding timeout for graceful exit 2010-05-21T00:50:47+00:00 Narendra Damahe ndamahe@nvidia.com 2010-05-20T23:00:59+00:00 6e671aaf8f56668efc809fbe757956c77f4046d8 Bug 679959 Change-Id: I71324cc89b4e3031ecc94ee5c05ba6193bab6533 Reviewed-on: http://git-master/r/1463 Reviewed-by: Narendra Damahe <ndamahe@nvidia.com> Tested-by: Narendra Damahe <ndamahe@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
Bug 679959

Change-Id: I71324cc89b4e3031ecc94ee5c05ba6193bab6533
Reviewed-on: http://git-master/r/1463
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
tegra usb-phy: Enable/disable Clock Over On bit for all controllers 2010-05-21T00:50:38+00:00 Venkat Moganty vmoganty@nvidia.com 2010-05-20T14:56:21+00:00 e25477a0cfb318f5030e4479b13f6d0722838d9c Enable Clock Over On bit for all three controllers during phy resume and disable during the suspend. Added timeout for the phy clock wait loops. Bug 679959 Tested on Ap20/Harmony. Change-Id: I3219946e6351c8ddf5e036dfc3a3f2b3693e99a6 Reviewed-on: http://git-master/r/1455 Reviewed-by: Seshendra Gadagottu <sgadagottu@nvidia.com> Tested-by: Seshendra Gadagottu <sgadagottu@nvidia.com> Reviewed-by: Narendra Damahe <ndamahe@nvidia.com> Tested-by: Narendra Damahe <ndamahe@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
Enable Clock Over On bit for all three controllers during phy resume and disable
during the suspend. Added timeout for the phy clock wait loops.

Bug 679959

Tested on Ap20/Harmony.

Change-Id: I3219946e6351c8ddf5e036dfc3a3f2b3693e99a6
Reviewed-on: http://git-master/r/1455
Reviewed-by: Seshendra Gadagottu <sgadagottu@nvidia.com>
Tested-by: Seshendra Gadagottu <sgadagottu@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
nvmap: fix unpin/pin race condition with RECLAIM_UNPINNED_VM 2010-05-21T00:50:27+00:00 Antti Hatala ahatala@nvidia.com 2010-05-20T10:48:41+00:00 c91243547a3c1b1d4a25b92582db7cd3b78b394f _nvmap_handle_unpin needs to acquire the mru_vma_lock before decrementing the pin count, to ensure that a decrement to zero and insertion on the MRU VMA list appears atomic with respect to a second client calling _nvmap_handle_pin on the same handle; otherwise, the two clients race and the pin operation may trigger a BUG because the handle has a valid IOVMM area but is not located on any MRU VMA list. also, clean up some additional allocation-inside-spinlock issues; release the MRU VMA lock before calling tegra_iovmm_create_vm, and reacquire the lock after returning. Change-Id: If3a32e493a9222eac56a0980c10c0d4281389e7e Reviewed-on: http://git-master/r/1448 Tested-by: Antti Hatala <ahatala@nvidia.com> Reviewed-by: Antti Hatala <ahatala@nvidia.com> 
_nvmap_handle_unpin needs to acquire the mru_vma_lock before decrementing
the pin count, to ensure that a decrement to zero and insertion on the
MRU VMA list appears atomic with respect to a second client calling
_nvmap_handle_pin on the same handle; otherwise, the two clients race
and the pin operation may trigger a BUG because the handle has a valid
IOVMM area but is not located on any MRU VMA list.

also, clean up some additional allocation-inside-spinlock issues;
release the MRU VMA lock before calling tegra_iovmm_create_vm, and
reacquire the lock after returning.

Change-Id: If3a32e493a9222eac56a0980c10c0d4281389e7e
Reviewed-on: http://git-master/r/1448
Tested-by: Antti Hatala <ahatala@nvidia.com>
Reviewed-by: Antti Hatala <ahatala@nvidia.com>
tegra kernel: Fixed version mismatch error. 2010-05-21T00:49:42+00:00 vdumpa vdumpa@nvidia.com 2010-05-19T22:43:31+00:00 1b0b9bb2adac5af3422364a64c627e3bf1741672 Bug 687750 Fixed version mismatch error between prebuilt kernel modules and locally built zImage files. Change-Id: Ia7d2f08270eab00d94359e085e807d15cb43b86a Reviewed-on: http://git-master/r/1446 Reviewed-by: Krishna Reddy <vdumpa@nvidia.com> Tested-by: Krishna Reddy <vdumpa@nvidia.com> Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com> 
Bug 687750
Fixed version mismatch error between prebuilt kernel modules
and locally built zImage files.

Change-Id: Ia7d2f08270eab00d94359e085e807d15cb43b86a
Reviewed-on: http://git-master/r/1446
Reviewed-by: Krishna Reddy <vdumpa@nvidia.com>
Tested-by: Krishna Reddy <vdumpa@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
tegra usb-phy: Fix UTMI/ULPI LP0 issues. 2010-05-21T00:49:12+00:00 Venkat Moganty vmoganty@nvidia.com 2010-05-19T16:17:53+00:00 754f91b0662286cf37916bca72444e7521eb4f0a UTMIP pads were turned off before the UTMI phy is set in to the suspend mode. This is corrected by turning off the UTMIP power control pads after phy is suspended. Added workaround for ULPI to bring out of suspend by setting USB2_CLK_OVR_ON bit in CLK_RST_CONTROLLER register. Bug 679959 Tested on Ap20/Harmony with Lp0 suspend/resume tests. Change-Id: I6519568f20c4cd859c198d82c2a3007305a61317 Reviewed-on: http://git-master/r/1413 Reviewed-by: Bitan Biswas <bbiswas@nvidia.com> Tested-by: Bitan Biswas <bbiswas@nvidia.com> Reviewed-by: Narendra Damahe <ndamahe@nvidia.com> Tested-by: Narendra Damahe <ndamahe@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
UTMIP pads were turned off before the UTMI phy is set in to the suspend mode.
This is corrected by turning off the UTMIP power control pads after phy is
suspended.
Added workaround for ULPI to bring out of suspend by setting USB2_CLK_OVR_ON
bit in CLK_RST_CONTROLLER register.

Bug 679959

Tested on Ap20/Harmony with Lp0 suspend/resume tests.

Change-Id: I6519568f20c4cd859c198d82c2a3007305a61317
Reviewed-on: http://git-master/r/1413
Reviewed-by: Bitan Biswas <bbiswas@nvidia.com>
Tested-by: Bitan Biswas <bbiswas@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
tegra power: Don't power gate the TD partition. 2010-05-21T00:49:03+00:00 tkasivajhula tkasivajhula@nvidia.com 2010-05-19T01:47:12+00:00 dac4511a0c9f0bcb57b03562cdcd5fe6cee02155 Occasionally, ungating the TD partition when exiting LP0 causes the entire system to crash. This WAR avoids this issue by keeping the TD partition always on. Change-Id: I20e09b3014feb011f922e654e2fb6d28a956d693 Reviewed-on: http://git-master/r/1435 Reviewed-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com> Tested-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com> Reviewed-by: Aleksandr Frid <afrid@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
Occasionally, ungating the TD partition when exiting
LP0 causes the entire system to crash. This WAR
avoids this issue by keeping the TD partition always on.

Change-Id: I20e09b3014feb011f922e654e2fb6d28a956d693
Reviewed-on: http://git-master/r/1435
Reviewed-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com>
Tested-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com>
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
[ARM/tegra] usbphy: partial revert of assignment != comparison 2010-05-21T00:48:53+00:00 Gary King gking@nvidia.com 2010-05-18T04:06:42+00:00 2f9602244b8da68c386b803ec3265b7245ae994a the assignment to hDdkUsbPhy->IsHostMode was intentional; rewrite the code to make this clearer Change-Id: Ifc881397c240049b7c0a4300ae3267be397bfda5 Reviewed-on: http://git-master/r/1420 Reviewed-by: Gary King <gking@nvidia.com> Tested-by: Gary King <gking@nvidia.com> 
the assignment to hDdkUsbPhy->IsHostMode was intentional; rewrite the
code to make this clearer

Change-Id: Ifc881397c240049b7c0a4300ae3267be397bfda5
Reviewed-on: http://git-master/r/1420
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
tegra mmc: enable MMC_UNSAFE_RESUME config for tegra_harmony_android 2010-05-17T22:05:23+00:00 Deepesh Gujarathi dgujarathi@nvidia.com 2010-05-17T14:55:21+00:00 b42da727f2243bad6801adb704fedaf16fa8fb7f Normally, when the system goes into suspend, all the storage cards are removed and later re-enumerated upon resume. During re-enumeration the device name and number are not guaranteed to be the same as they were during bootup. This can cause data corruption on cards. When the MMC_UNSAFE_RESUME config is enabled, it will prevent kernel from unmounting the mmc cards before suspend. Upon resume the cards will still be using the same device id as they were before suspend. This change seems to fix a lot of mmc related issues that occur during LP0 transitions. partial fix for Bug 679959 Change-Id: Ib90f95ebbc81c5b6e9e83e740ece31f914a262eb Reviewed-on: http://git-master/r/1412 Reviewed-by: Narendra Damahe <ndamahe@nvidia.com> Tested-by: Narendra Damahe <ndamahe@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
Normally, when the system goes into suspend, all the storage cards are
removed and later re-enumerated upon resume. During re-enumeration the
device name and number are not guaranteed to be the same as they were
during bootup. This can cause data corruption on cards.

When the MMC_UNSAFE_RESUME config is enabled, it will prevent kernel
from unmounting the mmc cards before suspend. Upon resume the cards
will still be using the same device id as they were before suspend.

This change seems to fix a lot of mmc related issues that occur
during LP0 transitions.

partial fix for Bug 679959

Change-Id: Ib90f95ebbc81c5b6e9e83e740ece31f914a262eb
Reviewed-on: http://git-master/r/1412
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
[ARM/tegra] usbphy: assignment != comparison 2010-05-17T19:06:35+00:00 Gary King gking@nvidia.com 2010-05-17T17:45:33+00:00 5e337a4f2e855515dab8c0bac217c8db500d7841 Change-Id: Id3d6b1575329b3ad1a763488a442449774f9d4e1 Reviewed-on: http://git-master/r/1414 Reviewed-by: Narendra Damahe <ndamahe@nvidia.com> Tested-by: Narendra Damahe <ndamahe@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
Change-Id: Id3d6b1575329b3ad1a763488a442449774f9d4e1
Reviewed-on: http://git-master/r/1414
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>