linux-toradex.git/drivers, branch tegra-9.12.13 Linux kernel for Apalis and Colibri modules nvec_keyboard:Correcting Virtual code for Escape Key 2010-06-03T01:29:11+00:00 Sachin Nikam snikam@nvidia.com 2010-06-01T10:10:23+00:00 04d40539e0032c5b7a729e6a4fb45602dce5327c On LDK there is no .kl file refered for keyboard. In code_tab_102us array corrected the Virtual code for Escape Key. From linux/input.h key 1 is KEY_ESC and not KEY_BACK Verified on LDK with firefox. Bug 684439 Change-Id: If52980f8c405ab96036778e9c3615ca76626c451 Reviewed-on: http://git-master/r/1914 Tested-by: Sachin Nikam <snikam@nvidia.com> Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-by: Sachin Nikam <snikam@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
On LDK there is no .kl file refered for keyboard.
In code_tab_102us array corrected the Virtual code for Escape Key.
From linux/input.h key 1 is KEY_ESC and not KEY_BACK
Verified on LDK with firefox.

Bug 684439

Change-Id: If52980f8c405ab96036778e9c3615ca76626c451
Reviewed-on: http://git-master/r/1914
Tested-by: Sachin Nikam <snikam@nvidia.com>
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
tegra sdhci: Enabling sdio cards suspend/resume 2010-06-02T16:44:58+00:00 Rahul Bansal rbansal@nvidia.com 2010-05-28T06:29:20+00:00 39e090b49c224778b5b83ac05ec948dffb717f3b SDIO-WIFI Behavior - 1) With or without MMC_UNSAFE_RESUME setting - As "sdio_driver" in mmc stack doesn't have suspend/resume handlers so even if MMC_UNSAFE_RESUME is set, SDIO-WIFI driver's remove/probe is called for mmc suspend/resume. Thus, on suspend (LP1 or LP0) wifi is turned off and is disconnected. On resume (from LP1 or LP0), wifi is turned on and is reconnected. 2) For all cards including sdio, power to rail is cut. On suspend for sdio slot NvOdmSdioSuspend() is called. On resume for sdio slot NvOdmSdioResume() is called. Change-Id: I52e65b08a884a16f47cf5b1e4fcbb187ea4281e6 Reviewed-on: http://git-master/r/1776 Reviewed-by: Kapil Hali <khali@nvidia.com> Reviewed-by: Pavan Kunapuli <pkunapuli@nvidia.com> Reviewed-by: Rahul Bansal <rbansal@nvidia.com> Tested-by: Rahul Bansal <rbansal@nvidia.com> Reviewed-by: Narendra Damahe <ndamahe@nvidia.com> Tested-by: Narendra Damahe <ndamahe@nvidia.com> Tested-by: Rakesh Goyal <rgoyal@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
SDIO-WIFI Behavior -
1) With or without MMC_UNSAFE_RESUME setting -
As "sdio_driver" in mmc stack doesn't have suspend/resume handlers
so even if MMC_UNSAFE_RESUME is set, SDIO-WIFI driver's remove/probe
is called for mmc suspend/resume.
Thus, on suspend (LP1 or LP0) wifi is turned off and is disconnected.
On resume (from LP1 or LP0), wifi is turned on and is reconnected.

2) For all cards including sdio, power to rail is cut.
On suspend for sdio slot NvOdmSdioSuspend() is called.
On resume for sdio slot NvOdmSdioResume() is called.

Change-Id: I52e65b08a884a16f47cf5b1e4fcbb187ea4281e6
Reviewed-on: http://git-master/r/1776
Reviewed-by: Kapil Hali <khali@nvidia.com>
Reviewed-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-by: Rahul Bansal <rbansal@nvidia.com>
Tested-by: Rahul Bansal <rbansal@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Rakesh Goyal <rgoyal@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
kernel:Fixing Kernel Compilation warnings. 2010-06-02T15:52:11+00:00 Sachin Nikam snikam@nvidia.com 2010-06-01T07:22:42+00:00 38a9d99c28da41805ebde7f85f4c0d377684da4e Warnings like: assignment from incompatible poiner type initialization from incompatible poiner type Bug 682070 Change-Id: Ia79b13a5a46ca884d333a971cff167da8cd89c40 Reviewed-on: http://git-master/r/1903 Reviewed-by: Venu Byravarasu <vbyravarasu@nvidia.com> Tested-by: Sachin Nikam <snikam@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
Warnings like:
assignment from incompatible poiner type
initialization from incompatible poiner type

Bug 682070

Change-Id: Ia79b13a5a46ca884d333a971cff167da8cd89c40
Reviewed-on: http://git-master/r/1903
Reviewed-by: Venu Byravarasu <vbyravarasu@nvidia.com>
Tested-by: Sachin Nikam <snikam@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
tegra: [RTC Alarm Clock] implement TI pmu tps6586x by PMIC (pwr_int) pin 2010-06-01T10:13:32+00:00 Wilson Chen wichen@nvidia.com 2010-05-27T14:51:56+00:00 5645d492c7ddb74c23f10b4daa479b333069516b Bug 631330 Bug 690351 Bug 690993 Tested on Ap20/Harmony. Change-Id: Id29c5fc8f5078ad4cb3aa1e43d0440c21ddd1a96 Reviewed-on: http://git-master/r/1725 Reviewed-by: Janne Hellsten <jhellsten@nvidia.com> Tested-by: Janne Hellsten <jhellsten@nvidia.com> 
Bug 631330
Bug 690351
Bug 690993

Tested on Ap20/Harmony.

Change-Id: Id29c5fc8f5078ad4cb3aa1e43d0440c21ddd1a96
Reviewed-on: http://git-master/r/1725
Reviewed-by: Janne Hellsten <jhellsten@nvidia.com>
Tested-by: Janne Hellsten <jhellsten@nvidia.com>
warnings: Fixing kernel compilation warnings. 2010-05-27T14:42:58+00:00 Sachin Nikam snikam@nvidia.com 2010-05-25T08:14:14+00:00 c3be44e23d3a57643cb12f8369cf26e9ad339988 Bug 682070 Change-Id: Ieff4ca65dc7034786ddfe0657585d66957bc7f3d Reviewed-on: http://git-master/r/1577 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-by: Sachin Nikam <snikam@nvidia.com> Tested-by: Sachin Nikam <snikam@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
Bug 682070

Change-Id: Ieff4ca65dc7034786ddfe0657585d66957bc7f3d
Reviewed-on: http://git-master/r/1577
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
Tested-by: Sachin Nikam <snikam@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
ldk usb: usb device detection at boot-time on USB1 (OTG) 2010-05-27T14:40:09+00:00 Abhishek Aggarwal aaggarwal@nvidia.com 2010-05-24T13:12:19+00:00 ae3a36307f58e03f9a1e1d3d4e790a96cd4e23ef 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: I66c82fe33228734dddba325a203ed54347993b1d Bug: 682618 Reviewed-on: http://git-master/r/1541 Tested-by: Abhishek Aggarwal <aaggarwal@nvidia.com> Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com> Tested-by: Hanumanth Venkateswa Moganty <vmoganty@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: I66c82fe33228734dddba325a203ed54347993b1d
Bug: 682618
Reviewed-on: http://git-master/r/1541
Tested-by: Abhishek Aggarwal <aaggarwal@nvidia.com>
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
nvmap: allow pinning handles without local context 2010-05-27T08:11:09+00:00 Anssi Kalliolahti akalliolahti@nvidia.com 2010-05-26T07:37:13+00:00 10f48922980ac0717b180e23416f6530f3152fbe This reverts partially the commit 46d2a32 "nvmap: tighten handle validation before pinning". It appears that we still need to allow pinning handles without local context (bug 691715). This can be reverted when the root cause gets fixed. Change-Id: I44cbd97f096d1319c6ea82c0d40030506547fd6c Reviewed-on: http://git-master/r/1632 Reviewed-by: Patrick Shehane <pshehane@nvidia.com> Tested-by: Patrick Shehane <pshehane@nvidia.com> Reviewed-by: Antti Hatala <ahatala@nvidia.com> 
This reverts partially the commit 46d2a32 "nvmap: tighten handle validation
before pinning".

It appears that we still need to allow pinning handles without local
context (bug 691715). This can be reverted when the root cause gets fixed.

Change-Id: I44cbd97f096d1319c6ea82c0d40030506547fd6c
Reviewed-on: http://git-master/r/1632
Reviewed-by: Patrick Shehane <pshehane@nvidia.com>
Tested-by: Patrick Shehane <pshehane@nvidia.com>
Reviewed-by: Antti Hatala <ahatala@nvidia.com>
tegra serial: adding power control api for bluesleep power management. 2010-05-26T01:35:41+00:00 Laxman Dewangan ldewangan@nvidia.com 2010-05-23T16:37:01+00:00 57ac37ef1a0a7840acec8525af4bca6933001c86 Adding apis for following function to hooking up tegra serial driver with bluesleep power management: - Clock off. - Clock on. - Setting flow control to desired state. - Checking for tx fifo status. Following 4 state machine is developed to achieve this: UART_CLOSED, UART_OPENED, UART_SUSPEND, UART_CLOCK_OFF. The transitions of state machines are as follows: UART_CLOSED: the init state on which resource is allocated but not opened by client or device is closed. UART_OPENED: Able to do data transfer. CLOSED to OPENED by opening the port. CLOCK_OFF to OPENED by calling function tegra_uart_request_clock_on(). SUSPEND to OPENED by calling resume(). UART_CLOCK_OFF: The controller clock is disabled and so no data transfer can happen. At this state, controller is not ready for deep power down. OPENED to CLOCK_OFF by calling tegra_uart_request_clock_off(). Can not go to this state from CLOSED and SUSPEND. UART_SUSPEND: The controller is in suspended state and ready for deep power down. UART_CLOCK_OFF to SUSPEND: OPENED to SUSPEND. Tested in whistler. Change-Id: I24461ac6f20f61e44b49332cdc6b93a01f605fc9 Reviewed-on: http://git-master/r/1377 Reviewed-by: Udaykumar Rameshchan Raval <uraval@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> Tested-by: Gary King <gking@nvidia.com> 
Adding apis for following function to hooking up tegra serial driver with
bluesleep power management:
 - Clock off.
 - Clock on.
 - Setting flow control to desired state.
 - Checking for tx fifo status.

Following 4 state machine is developed to achieve this:
UART_CLOSED, UART_OPENED, UART_SUSPEND, UART_CLOCK_OFF.

The transitions of state machines are as follows:
UART_CLOSED: the init state  on which resource is allocated but not
  opened by client or device is closed.

UART_OPENED: Able to do data transfer.
  CLOSED  to  OPENED by opening the port.
  CLOCK_OFF to OPENED by calling function tegra_uart_request_clock_on().
  SUSPEND to OPENED by calling resume().

UART_CLOCK_OFF: The controller clock is disabled and so no data transfer
 can happen. At this state, controller is not ready for deep power down.
 OPENED to CLOCK_OFF by calling tegra_uart_request_clock_off().
 Can not go to this state from CLOSED and SUSPEND.

UART_SUSPEND: The controller is in suspended state and ready for deep power down.
 UART_CLOCK_OFF to SUSPEND:
 OPENED to SUSPEND.

Tested in whistler.

Change-Id: I24461ac6f20f61e44b49332cdc6b93a01f605fc9
Reviewed-on: http://git-master/r/1377
Reviewed-by: Udaykumar Rameshchan Raval <uraval@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
tegra framebuffer - dsi one shot support 2010-05-25T17:44:01+00:00 Arthur Spence aspence@nvidia.com 2010-05-20T20:25:29+00:00 16624522eb677d10c3846f25283f95530a7d5017 DSI one shot support requires register access in the tegra framebuffer to poke the frame trigger bit (with both the trigger bit and the tearing effect signal are high, a frame of pixels will be sent to the panel). The boot args must also be expanded to have a "use tearing effect" flag. Change-Id: Id0c3960cac5b59dd23fd6547f1b7dae4d422ac32 Reviewed-on: http://git-master/r/1460 Reviewed-by: Gary King <gking@nvidia.com> Tested-by: Arthur Spence <aspence@nvidia.com> 
DSI one shot support requires register access in the tegra framebuffer to
poke the frame trigger bit (with both the trigger bit and the tearing effect
signal are high, a frame of pixels will be sent to the panel). The boot args
must also be expanded to have a "use tearing effect" flag.

Change-Id: Id0c3960cac5b59dd23fd6547f1b7dae4d422ac32
Reviewed-on: http://git-master/r/1460
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Arthur Spence <aspence@nvidia.com>
nvmap: tighten handle validation before pinning 2010-05-21T15:57:55+00:00 Anssi Kalliolahti akalliolahti@nvidia.com 2010-05-20T11:45:03+00:00 46d2a32a664e9c80ac78001b00ba6b7b23d44249 Do not allow pinning handles without local context anymore (this was a special case and is not needed anymore). Also, added check for handle poison before pinning. This prevents kernel panic (BUG_ON in _nvmap_handle_pin_locked) when trying to pin already freed handle. Change-Id: Iabf408c182aa0907596957233169568abedbbb1f Reviewed-on: http://git-master/r/1449 Reviewed-by: Antti Rasmus <arasmus@nvidia.com> Tested-by: Anssi Kalliolahti <akalliolahti@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
Do not allow pinning handles without local context anymore (this was a
special case and is not needed anymore). Also, added check for handle poison
before pinning. This prevents kernel panic (BUG_ON in
_nvmap_handle_pin_locked) when trying to pin already freed handle.

Change-Id: Iabf408c182aa0907596957233169568abedbbb1f
Reviewed-on: http://git-master/r/1449
Reviewed-by: Antti Rasmus <arasmus@nvidia.com>
Tested-by: Anssi Kalliolahti <akalliolahti@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>