linux-toradex.git, branch tegra-10.11.10 Linux kernel for Apalis and Colibri modules tegra: dc: set HDMI clock to 0 if HDMI unplugged 2011-06-18T00:03:50+00:00 Xin Xie xxie@nvidia.com 2011-05-27T22:58:08+00:00 e299e1d21b790cc390c4176b963904c13bfa4c9b HDMI clock is not auto dvfs, so we need set the clock rate to 0 if HDMI is disabled. Otherwise the Vdd core voltage will be always 1.2v even after HDMI cable unplugged. BUG 828306 Reviewed-on: http://git-master/r/34379 (cherry picked from commit 58ddd144a6c2dd9bbc9d2f3c8b1e025364d88c22) Change-Id: I5b455a7a945d4834fb162b2986639df5a26b112c Reviewed-on: http://git-master/r/37176 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Tested-by: Bharat Nihalani <bnihalani@nvidia.com> Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com> 
HDMI clock is not auto dvfs, so we need set the clock rate to 0 if HDMI
is disabled. Otherwise the Vdd core voltage will be always 1.2v even
after HDMI cable unplugged.

BUG 828306

Reviewed-on: http://git-master/r/34379
(cherry picked from commit 58ddd144a6c2dd9bbc9d2f3c8b1e025364d88c22)

Change-Id: I5b455a7a945d4834fb162b2986639df5a26b112c
Reviewed-on: http://git-master/r/37176
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
usb: gadget: f_mass_storage: Make us pass USBCV MSC Compliance tests 2011-06-17T06:00:14+00:00 Rakesh Bodla rbodla@nvidia.com 2011-06-13T11:57:05+00:00 39c30df208e8ede3b7c2be58d630fb97c983f87b Defer the SET_CONFIG and SET_INTERFACE control transfer's data/status stages till we are ready to process new CBW from the host. This way we ensure that we don't loose any CBW during MSC compliance tests and cause lock up. (cherry picked from commit 95ed32366748e2034e82c9e738c312df8fb3d3a9) Change-Id: Ib8c7140d11f558c969802558476ff6013aae3269 Reviewed-on: http://git-master/r/36275 Reviewed-by: Rohan Somvanshi <rsomvanshi@nvidia.com> Tested-by: Rohan Somvanshi <rsomvanshi@nvidia.com> 
Defer the SET_CONFIG and SET_INTERFACE control transfer's data/status
stages till we are ready to process new CBW from the host. This way we
ensure that we don't loose any CBW during MSC compliance tests and cause
lock up.

(cherry picked from commit 95ed32366748e2034e82c9e738c312df8fb3d3a9)

Change-Id: Ib8c7140d11f558c969802558476ff6013aae3269
Reviewed-on: http://git-master/r/36275
Reviewed-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
Tested-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
mmc: tegra: disable broken deferred resume 2011-06-17T01:32:34+00:00 David Schalig dschalig@nvidia.com 2011-06-02T13:17:14+00:00 191aa3eb0f06f082e10d055080e91a9a25b9492e MMC_BLOCK_DEFERRED_RESUME causes race conditions in the SD/MMC driver, i.e. mmc_sd_detect() will be called from different threads causing inconsistent state. Disabling feature for Tegra. Bug 833034 http://git-master/r/#change,36254 (cherry picked from commit a8b6bb5de9b9645ecdabc3e954f04898e45e9038) Change-Id: Ie28fa42e28ab98d8bffef7e48591cbec98af5fe2 Reviewed-on: http://git-master/r/36430 Reviewed-by: Yuhao Ding <yding@nvidia.com> Tested-by: Yuhao Ding <yding@nvidia.com> 
MMC_BLOCK_DEFERRED_RESUME causes race conditions in the SD/MMC driver,
i.e. mmc_sd_detect() will be called from different threads causing
inconsistent state. Disabling feature for Tegra.

Bug 833034

http://git-master/r/#change,36254
(cherry picked from commit a8b6bb5de9b9645ecdabc3e954f04898e45e9038)

Change-Id: Ie28fa42e28ab98d8bffef7e48591cbec98af5fe2
Reviewed-on: http://git-master/r/36430
Reviewed-by: Yuhao Ding <yding@nvidia.com>
Tested-by: Yuhao Ding <yding@nvidia.com>
mmc: fix card detect after suspend 2011-06-17T01:26:20+00:00 David Schalig dschalig@nvidia.com 2011-06-01T09:32:13+00:00 e69f9291f85c4eeaa02091111a8fc8835efe333e If defered SD card resume (CONFIG_MMC_BLOCK_DEFERRED_RESUME) is enabled, PM_POST_SUSPEND handler will never set host->rescan_disable back to 0, and card detect logic will be disabled forever. fix missing break fix incorrect cleanup sequences Bug 833034 http://git-master/r/#change,36251 (cherry picked from commit 31d509d8e2e2b7c35da69029f932d35c3995fe36) Change-Id: I3e513359af68e92476d693f4d1751b4b0d883569 Reviewed-on: http://git-master/r/36429 Reviewed-by: David Schalig <dschalig@nvidia.com> Tested-by: David Schalig <dschalig@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
If defered SD card resume (CONFIG_MMC_BLOCK_DEFERRED_RESUME) is enabled,
PM_POST_SUSPEND handler will never set host->rescan_disable back to 0,
and card detect logic will be disabled forever.

fix missing break

fix incorrect cleanup sequences

Bug 833034

http://git-master/r/#change,36251
(cherry picked from commit 31d509d8e2e2b7c35da69029f932d35c3995fe36)

Change-Id: I3e513359af68e92476d693f4d1751b4b0d883569
Reviewed-on: http://git-master/r/36429
Reviewed-by: David Schalig <dschalig@nvidia.com>
Tested-by: David Schalig <dschalig@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
ARM: tegra: confiure AHBDMA gizmo setting. 2011-06-17T01:26:14+00:00 Jay Cheng jacheng@nvidia.com 2011-06-09T21:34:35+00:00 c3adbb7631627dc14c864a4d9ab8fd2e8e319c2d Bug 820602 Reviewed-on: http://git-master/r/35954 (cherry picked from commit 2d6cac283c1121b9a90b742b5dcf80141422eac6) Change-Id: I6149c878061bace0c191a0d45ddd7e5b8ffce4cd Reviewed-on: http://git-master/r/36683 Tested-by: Rakesh Bodla <rbodla@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
Bug 820602

Reviewed-on: http://git-master/r/35954
(cherry picked from commit 2d6cac283c1121b9a90b742b5dcf80141422eac6)
Change-Id: I6149c878061bace0c191a0d45ddd7e5b8ffce4cd
Reviewed-on: http://git-master/r/36683
Tested-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
ARM: tegra: pm: save/restore ahb bus registers 2011-06-17T01:26:09+00:00 Jay Cheng jacheng@nvidia.com 2011-06-09T21:15:20+00:00 d5743e9dfddaa3d41ecd729733c66e4ac54a13d7 Bug 814896, 820602 Reviewed-on: http://git-master/r/35948 (cherry picked from commit 4b9158b73bd5b5ae9b1059d31e062362d4732064) Change-Id: I2ac442aa45eb11b47a97320524f7b82d9f2296d7 Reviewed-on: http://git-master/r/36675 Tested-by: Rakesh Bodla <rbodla@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
Bug 814896, 820602

Reviewed-on: http://git-master/r/35948
(cherry picked from commit 4b9158b73bd5b5ae9b1059d31e062362d4732064)

Change-Id: I2ac442aa45eb11b47a97320524f7b82d9f2296d7
Reviewed-on: http://git-master/r/36675
Tested-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
usb: gadget: composite: Allow function drivers to pause control transfers 2011-06-17T01:26:02+00:00 Rakesh Bodla rbodla@nvidia.com 2011-06-13T11:49:34+00:00 ccb7b4793e54d6367430b2c42bcfadbe18ff365d Some USB function drivers (e.g. f_mass_storage.c) need to delay or defer the data/status stages of standard control requests like SET_CONFIGURATION or SET_INTERFACE till they are done with their bookkeeping and are actually ready for accepting new commands to their interface. They can now achieve this functionality by returning USB_GADGET_DELAYED_STATUS in their setup handlers (e.g. set_alt()). The composite framework will then defer completion of the control transfer by not completing the data/status stages. This ensures that the host does not send new packets to the interface till the function driver is ready to take them. When the function driver that requested for USB_GADGET_DELAYED_STATUS is done with its bookkeeping, it should signal the composite framework to continue with the data/status stages of the control transfer. It can do so by invoking the new API usb_composite_setup_continue(). This is where the control transfer's data/status stages are completed and host can initiate new transfers. The DELAYED_STATUS mechanism is currently only supported if the expected data phase is 0 bytes (i.e. w_length == 0). Since SET_CONFIGURATION and SET_INTERFACE are the only cases that will use this mechanism, this is not a limitation. (cherry picked from commit 1b9ba000177ee47bcc5b44c7c34e48e735f5f9b1) Change-Id: I4aaf702e03898573f92e58223a29eafbc9612219 Reviewed-on: http://git-master/r/36273 Tested-by: Rakesh Bodla <rbodla@nvidia.com> Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com> 
Some USB function drivers (e.g. f_mass_storage.c) need to delay or defer the
data/status stages of standard control requests like SET_CONFIGURATION or
SET_INTERFACE till they are done with their bookkeeping and are actually ready
for accepting new commands to their interface.

They can now achieve this functionality by returning USB_GADGET_DELAYED_STATUS
in their setup handlers (e.g. set_alt()). The composite framework will then
defer completion of the control transfer by not completing the data/status stages.

This ensures that the host does not send new packets to the interface till the
function driver is ready to take them.

When the function driver that requested for USB_GADGET_DELAYED_STATUS is done
with its bookkeeping, it should signal the composite framework to continue with
the data/status stages of the control transfer. It can do so by invoking
the new API usb_composite_setup_continue(). This is where the control transfer's
data/status stages are completed and host can initiate new transfers.

The DELAYED_STATUS mechanism is currently only supported if the expected data phase
is 0 bytes (i.e. w_length == 0). Since SET_CONFIGURATION and SET_INTERFACE are the
only cases that will use this mechanism, this is not a limitation.

(cherry picked from commit 1b9ba000177ee47bcc5b44c7c34e48e735f5f9b1)

Change-Id: I4aaf702e03898573f92e58223a29eafbc9612219
Reviewed-on: http://git-master/r/36273
Tested-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
usb: gadget: f_mass_storage: Fix Bulk-only RESET handling 2011-06-17T01:25:56+00:00 Rakesh Bodla rbodla@nvidia.com 2011-06-13T11:53:38+00:00 6fbd5ae6491399581c4c719789c7e9259d40c504 The ep0 request tag was not recorded thus resulting in phase problems while sending status/response in handle_execption() handler. This was resulting in MSC compliance test failures with USBCV tool. With this patch, the Bulk-Only Mass storage RESET request is handled correctly and the MSC compliance tests pass. (cherry picked from commit 73ee4da994e7b97bd8241e39099cf3dd94675d79) Change-Id: Ia5beffe1e38b518b63b80dda36faf06b86f7a6cb Reviewed-on: http://git-master/r/36274 Tested-by: Rakesh Bodla <rbodla@nvidia.com> Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com> 
The ep0 request tag was not recorded thus resulting in phase
problems while sending status/response in handle_execption() handler.
This was resulting in MSC compliance test failures with USBCV tool.

With this patch, the Bulk-Only Mass storage RESET request is
handled correctly and the MSC compliance tests pass.

(cherry picked from commit 73ee4da994e7b97bd8241e39099cf3dd94675d79)

Change-Id: Ia5beffe1e38b518b63b80dda36faf06b86f7a6cb
Reviewed-on: http://git-master/r/36274
Tested-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
drivers: net: wireless :bcm4329: disable sdio interrupts before wifi reset 2011-06-17T01:24:51+00:00 Rahul Bansal rbansal@nvidia.com 2011-06-15T14:33:44+00:00 113676ec197fc62b7dce23dad4e081c940319846 during system suspend if wifi is on but not connected, android sets RTC alarm to wake up system after 2 mins of system suspend to turn off wifi. during turning off wifi it was observed that BCM4329 MAC is giving spurious sdio interrupts which was causing lockup issue (mmc_lock) between sdio interrupt handling process and wifi stop process, to fix this issue sdio interrupts are disabled before giving MAC reset from host. Bug 834444 Bug 798783 Bug 796147 Bug 797230 Bug 780047 Bug 818687 Change-Id: I98ac26ca8951bb9f32dcff06e096d1ac9c9e3788 Reviewed-on: http://git-master/r/36755 Reviewed-by: Rahul Bansal <rbansal@nvidia.com> Tested-by: Rahul Bansal <rbansal@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
during system suspend if wifi is on but not connected, android
sets RTC alarm to wake up system after 2 mins of system suspend
to turn off wifi. during turning off wifi it was observed that
BCM4329 MAC is giving spurious sdio interrupts which was causing
lockup issue (mmc_lock) between sdio interrupt handling process
and wifi stop process, to fix this issue sdio interrupts are
disabled before giving MAC reset from host.

Bug 834444
Bug 798783
Bug 796147
Bug 797230
Bug 780047
Bug 818687

Change-Id: I98ac26ca8951bb9f32dcff06e096d1ac9c9e3788
Reviewed-on: http://git-master/r/36755
Reviewed-by: Rahul Bansal <rbansal@nvidia.com>
Tested-by: Rahul Bansal <rbansal@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
ARM: tegra: clocks: Add shared sclk for statmon 2011-06-16T05:30:09+00:00 Prashant Gaikwad pgaikwad@nvidia.com 2011-06-10T08:39:10+00:00 a19f85a8a7af722bcfd729297e682574dc22de7b H/W statistics monitor for AVP controls sclk depending on load. Instead of overriding avp.sclk rate, separate sclk client added for statmon so that busy hints from AVP can be handled. Bug 831892 Change-Id: Ieaa43525d7582810095a2200486019ae9b4a7553 Reviewed-on: http://git-master/r/36057 Reviewed-by: Prashant Gaikwad <pgaikwad@nvidia.com> Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com> Reviewed-by: Aleksandr Frid <afrid@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
H/W statistics monitor for AVP controls sclk depending on load.
Instead of overriding avp.sclk rate, separate sclk client added
for statmon so that busy hints from AVP can be handled.

Bug 831892

Change-Id: Ieaa43525d7582810095a2200486019ae9b4a7553
Reviewed-on: http://git-master/r/36057
Reviewed-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>