Fix for bug 688807. Function NvOdmKbcFilterKeys (ghost keys filter) was called only from bootloader keyboard driver, but not from OS driver. Fixed. Change-Id: Ibf8c0ccbf393e9c53a08a4cb2f746960bb43e4f8 Reviewed-on: http://git-master/r/3648 Tested-by: Victor Ryabukhin <vryabukhin@nvidia.com> Reviewed-by: Janne Hellsten <jhellsten@nvidia.com>
KBC driver should set the DPD override register before entering in to LP0. Also it should forcefully clear the interrupt status register to clear any pending status. Configuring the kbc rowmask register for allowing the key detection only from wakeup enabled keysi before suspend. Change-Id: I2b1b0e2cd7d0ffc10c2b2f6b2e88f79ab7fb687b Reviewed-on: http://git-master/r/3495 Tested-by: Abhishek Aggarwal <aaggarwal@nvidia.com> Reviewed-by: Narendra Damahe <ndamahe@nvidia.com> Tested-by: Narendra Damahe <ndamahe@nvidia.com> Reviewed-by: Aleksandr Frid <afrid@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Integrating warning fixes from kernel .29 to .32 Change-Id: I95f0dd92e830f80cae2fb4d3383c9efa845238a9 Reviewed-on: http://git-master/r/3176 Tested-by: Sachin Nikam <snikam@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
As these changes are causing power regressions on whistler, reverting them. Tested on: whistler Bug 702317 Change-Id: I025e1f4e7d58f020ced7dadff1707ac403d620ba Reviewed-on: http://git-master/r/3180 Reviewed-by: Bitan Biswas <bbiswas@nvidia.com> Tested-by: Bitan Biswas <bbiswas@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
Enabled Bosch and Kionix accelerometers together. Added an abstraction layer which would route calls to Bosch or Kionix accelerometer based on run time detection Testing done: observed changes in accelerometer readings when the device is moved. Change-Id: I7cdadb609703d6d0eeabf6e2878adb5f81c43b72 Reviewed-on: http://git-master/r/2753 Tested-by: Venu Byravarasu <vbyravarasu@nvidia.com> Reviewed-by: Hoang Pham <hopham@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
Touch screen drivers must report size value for presses. If size < 0.6, then it is considered finger press. If size > 0.6, then event is considered to be cheek press. The distinction is important in phone mode, because cheek presses are ignored in that mode (the user has the device next to his face in phone mode, and will likely press cheek accidentally against touch screen). Bug 700050 Change-Id: I6792a888f4761672230140e011e9fdc5d60696d3 Reviewed-on: http://git-master/r/2903 Reviewed-by: Michael Hsu <mhsu@nvidia.com> Tested-by: Michael Hsu <mhsu@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
Correct return value for key 1 is KEY_ESC, not KEY_BACK. Bug 684439 Change-Id: I55db604e79f9f9c3eed4e7dcb4538b096cdc69ae Reviewed-on: http://git-master/r/2566 Tested-by: Sachin Nikam <snikam@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
fix the infinite loop triggered by multi-touch controllers also, modify the multi-touch loops to loop over the number of fingers supported by the controller, rather than MAX_FINGERS bug 699471 Change-Id: I7c83aa87f9d5c75600cae36c1b40615903a95cec Reviewed-on: http://git-master/r/2747 Reviewed-by: Gary King <gking@nvidia.com> Tested-by: Gary King <gking@nvidia.com>
The kernel touch stack can support a max of 5 fingers at a time. Adding support in the driver to suport 5 fingers too. The touch odm for whistler is broken, hence disable pressure and width support. Change-Id: I9e148bab2efa0116a6513cc8b1cb2ffc2ea27cc8 Reviewed-on: http://git-master/r/2327 Tested-by: Varun Wadekar <vwadekar@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
Moved NvEc calls from nvec-keyboard driver to keyboard odm kit where all the remaining communication with NvEc resides. Change-Id: I12c528a7b54a02ccef5129d022934da3476e0fcf Reviewed-on: http://git-master/r/2471 Tested-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-by: Varun Wadekar <vwadekar@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>