Age | Commit message (Collapse) | Author |
|
This reverts commit 625cef6510b7c65fd043738fce577e017b415c0d.
Bug 1567183
Change-Id: I02f2b3cd20cc492737641632d9dace2a9702d2c8
Signed-off-by: Harry Hong <hhong@nvidia.com>
Reviewed-on: http://git-master/r/559682
|
|
Printing HDMI_5V0 enable/disable.
Bug 200008754
Change-Id: I370fc2afa7f0dd50610cd9a602a790cedefe9bfb
Signed-off-by: Harry Hong <hhong@nvidia.com>
Reviewed-on: http://git-master/r/441566
|
|
Printing smps10_ctrl&status reg value at read/write.
Bug 200008754
Change-Id: I6bde6506880e816d99c4c4c55d9a8d3987d71c8f
Signed-off-by: Harry Hong <hhong@nvidia.com>
Reviewed-on: http://git-master/r/440141
|
|
In order to check smps10_out1 enabling, read smps10_ctrl instead of
smps10_status.
In factory line, few board has no smps10_out1 output.
dc driver definitely enable smps10_out1 during booting and
disable/re-enable at suspend/resume.
No repro in SQA side and no chance to get the additional log
to identify this issue.
So, apply this change for the possible cause of it because
smps10_out1 will not be enabled if smps10_status reports true.
Bug 200008754
Change-Id: Icc39f1662ee274fbf2d6154811603cb3e7d12984
Signed-off-by: Harry Hong <hhong@nvidia.com>
Reviewed-on: http://git-master/r/439717
|
|
Prox state is changed during go into suspend, device loose it state.
Add wake lock 1 sec to prevent suspend when interrupt occur.
bug 200020300
Change-Id: I34901f4e32de9156ebbe36bf72b8d448f3f8fe9c
Signed-off-by: Hyong Bin Kim <hyongbink@nvidia.com>
Reviewed-on: http://git-master/r/438143
GVS: Gerrit_Virtual_Submit
Reviewed-by: Jackie Chen <jackchen@nvidia.com>
Tested-by: Jackie Chen <jackchen@nvidia.com>
Reviewed-by: Harry Hong <hhong@nvidia.com>
|
|
Add log to indicate the power key event.
Update the log info to be self-explanatory.
Bug 200011910
Bug 200012680
Change-Id: Ic06878fc65402c0b4d585967b0f0c7a22e41935c
Signed-off-by: Danny Song <dsong@nvidia.com>
Reviewed-on: http://git-master/r/423608
Reviewed-on: http://git-master/r/435525
|
|
Add log to indicate the power key event.
Bug 200011910
Bug 200012680
Change-Id: I462d4f1655529c0e964b77812d55d248be541eec
Signed-off-by: Danny Song <dsong@nvidia.com>
Reviewed-on: http://git-master/r/422752
GVS: Gerrit_Virtual_Submit
Reviewed-on: http://git-master/r/435524
|
|
To avoid error on csi, we do mipi calibration,
while camera is not on.
Bug 1490685
Bug 1504262
Change-Id: I91adb3da0ae54ccb4e0963f1f3f3cf933a292830
Signed-off-by: BK Kim <bkk@nvidia.com>
Reviewed-on: http://git-lge/r/1550
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
Reviewed-on: http://git-master/r/435540
|
|
When smooth_k is enabled, the NVSD driver determines
that hardware pixel gain and brightness calculations
are complete when it sees to consecutive and equal
brightness values. However, since multiple raw K
values are mapped to a single brightness value,
this check can be misleading.
To fix this, we continue checking for new brightness
values for a few additional frames after seeing repeating
brightness results. The number of frames is calculated
from smooth_k_incr.
Bug 1502587
Change-Id: I97f2ecd77398cf441ac720b6e306e0a1c89eed5d
Signed-off-by: Daniel Solomon <daniels@nvidia.com>
Reviewed-on: http://git-master/r/423871
(cherry picked from commit ce039a7a6d0f0b3764dc1e719b297fc37e343f45)
Reviewed-on: http://git-master/r/435077
Reviewed-by: Harry Hong <hhong@nvidia.com>
Tested-by: Harry Hong <hhong@nvidia.com>
|
|
Nvidia changes to update Maxim touch AVDD voltage setting.
Bug 1522154
Bug 200006060
Bug 1522162
Bug 1444604
Bug 1493749
Change-Id: I8a6d349fe9ceead294505597155e9fbb1323e1af
Signed-off-by: djung <djung@nvidia.com>
Reviewed-on: http://git-master/r/427871
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Harry Hong <hhong@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit 5303a5b7be5e1973152f9899c3b240f4118aa0ca.
Change-Id: I6274a3ae3699ac78a6facd4d57b72681b85511a5
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428085
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit 9f19268f389d16846713471dd5914bd269e1002c.
Change-Id: I42b130e06ab5103715fdc45c955071d62dcf76f0
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428083
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit f989de509c5c92d9d6f1b60ab44877f8b4f4a8fb.
Change-Id: Ica2944c936a14b643ffb7232fd50f9145e3daae9
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428082
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit b9896d8e565fb27f3e690556d6bd55d268f32470.
Change-Id: I118c3633d23822c41be5a2d9c5cce4ef423640b2
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428081
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit 14d9ab730e79a6a02f2737aaf77888d18881d322.
Change-Id: I66165659c999a60a48f615eff4de3c1c7e07bb7f
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428078
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit 97fb92fdabfdf799a1da4838cbc52bdbbb840e45.
Change-Id: Ia553b7bc713efc8acd08a85f74cfb7ddc7a64c15
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428077
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit 31223fc9c52af0713f7409cbbd7255fe287bf563.
Change-Id: I9a9d3f61d0fef35acd001a533954a92dfdc7477c
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428076
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit a96c9be87c663e1ec7b4105bb30a3c77357f405e.
Change-Id: Ibeae9abe43ec747853bbf25cd79c420b0bdf7da0
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428072
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit 5ac84f19d95ccde8725dc828073bb1aadeb80fab.
Change-Id: I9dbd047a4874d943121b736016c7c5bb9254cd00
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428071
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit 96c0b4253bf6dd331983250c5d92e96a74f794ba.
Change-Id: Ie1b04bf75cca8e919b1902722b7abf2104bc69f1
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428070
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit fd35fa2f2145ddc0a0cde5bc09c7483841f68613.
Change-Id: I7d83463345f5c24fdafe693b63082418bf19a230
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428069
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit 7ccccf232f78411846dfd617121f12d212c57c81.
Change-Id: I826a7cb256b05f5495191119bd05e3ce9a71423a
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428068
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit 44f8a9e1b9cb6ef709735ac247a2460a79624a80.
Change-Id: Ia8dd511636343dd8b1d484add87354c73bf59543
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428067
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit 2a698014d1e170b736237ad7f7caf046295c413b.
Change-Id: Ib68e1c3c9ff3c6f2e75a27741b1a197fceb38d20
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428063
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit e5ab87ee1c4f0c3f8557ddde3be07d43b94aae07.
Change-Id: I2805688d8be8b2b3bc67e408a5556970f38bd0af
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428075
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
DO NOT INTEGRATE
Bug 1466757
This reverts commit 37ad3e3e97d734e74e071bf5e8796b22e16814e4.
Change-Id: I709cd76ccc70aee7d768ace2463b85049cc420f3
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/428074
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
Updated touch power sequence to stay within tolerances.
Bug 15221534
Change-Id: Ic35bf958c5e93a1a8a454985be357eb3a8e866af
Signed-off-by: djung <djung@nvidia.com>
Reviewed-on: http://git-master/r/426695
Reviewed-by: Harry Hong <hhong@nvidia.com>
Tested-by: Harry Hong <hhong@nvidia.com>
|
|
Center offset is different each sensor mode.
Bug 200005968
Change-Id: I3a80abaacd71d05dae66bf30612899f2c50a101f
Signed-off-by: Karl Kim <kkim@nvidia.com>
Reviewed-on: http://git-master/r/415657
(cherry picked from commit 9d422ac409bab00ea307587a17b575b9f159cef7)
Reviewed-on: http://git-master/r/426540
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Peter Kim <pekim@nvidia.com>
|
|
added 6s delay to fork touch_fusion process to make sure hardware is
ready before calibration.
Bug 200006060
Change-Id: I6b24d2e4a7fa85165c76eb5badb7538e40021e7f
Signed-off-by: David Pu <dpu@nvidia.com>
Reviewed-on: http://git-master/r/423472
(cherry picked from commit 1abe1e63e61dc8f074fcd7eb8b28baaa3fa4a2ec)
Reviewed-on: http://git-master/r/424451
Reviewed-by: Harry Hong <hhong@nvidia.com>
Tested-by: Harry Hong <hhong@nvidia.com>
|
|
Some drivers send reports directly to underlying device, creating an
unwanted dependency on the underlying transport layer. This patch adds
hid_hw_request() to the interface, thereby removing usbhid from the
lion share of the drivers.
Bug 1466757
Signed-off-by: Henrik Rydberg <rydberg@euromail.se>
Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
(cherry picked from commit e90a6df80dc45ab53d2f4f4db297434e48c0208e)
Change-Id: I1c18daaf177c116e0665e16280199595f9b26dbd
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/411358
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417528
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
Make changes to the blake driver to support new features that were
enabled with new FW. This includes:
- Force feedback enablement
- Touchpad tweaking to improve UX
- New hid report support
Bug 1456586
Bug 1481171
Bug 1504937
Bug 1514012
Bug 1466757
Change-Id: Ibff4c23131cc341aa0400a28b47e740019d293b5
Signed-off-by: Ben Goska <bgoska@nvidia.com>
Reviewed-on: http://git-master/r/411102
(cherry picked from commit 3a34df6344390697b346c0b05f75e83117293894)
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/411357
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417527
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
Adding remove function to remove sysfs attribute nodes
when blake is disconnected.
Bug 200003632
Bug 1466757
Change-Id: I5bf571176d2653b9f74f548775da904ef93007c8
Signed-off-by: Vinayak Pane <vpane@nvidia.com>
Reviewed-on: http://git-master/r/410596
(cherry picked from commit 9904c21f42b14f3675c27ef2646eae669440bd07)
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/411356
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417526
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
Add device disconnect check in usbhid_get_raw_report()
Bug 200000762
Bug 1466757
Change-Id: Ia56a5ba746ee197a0be967f4cb09e38e44be8a8f
Signed-off-by: Vinayak Pane <vpane@nvidia.com>
Reviewed-on: http://git-master/r/409171
(cherry picked from commit 0c3a4ca1741ee9c1175af23e27ca0463c05c9872)
Reviewed-on: http://git-master/r/411355
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417525
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
-Mouse Mode(Default on KK): trackpad is functioning as
a mouse.
-Gesture Mode(Default on KKWT): trackpad is functioning
as a D-pad.
-Absolute Mode: trackpad is sending absolute coordinates
as ABS_X and ABS_Y.
-Disabled Mode: trackpad will not send anything to host.
Bug 1503137
Bug 1466757
Change-Id: Ifd007af18cafc0e1c34ba335cae9ee59e34e9e9f
Signed-off-by: Jun Yan <juyan@nvidia.com>
(cherry picked from commit a5c530a7f961c5c07b286766955cee37f919215e)
Reviewed-on: http://git-master/r/411354
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417524
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
The Freescale i.MX28 BootROM USB recovery mode implements the USB HID
protocol, yet the global item tag report size is 128. Linux checks if
this is 96 as of now, see [1]. This causes Linux to refuse to communicate
with this device, making it impossible to use the recovery mode.
This is not a standard HID device per se, but rather a software emulation
implemented within the BootROM code and realized through USB OTG-capable
port switched to device mode present on the device.
Previous attempt to discuss this issue dates back to 2011, see [2]. There
has been not much response. Also noteworthy is the [3], where there seems
to be a pointing device that has issue similar to this one.
The tool making use of the USB recovery mode is available at [4].
[1] http://comments.gmane.org/gmane.linux.kernel.input/22328
[2] http://www.spinics.net/lists/linux-usb/msg43463.html
[3] https://bbs.archlinux.org/viewtopic.php?pid=1141340
[4] http://git.bfuser.eu/?p=marex/mxsldr.git;a=summary
Bug 1466757
Bug 1506725
Change-Id: I32fb3e0e96c1509e445e5a073823ed06acd9db2c
Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Chen Peter <B29397@freescale.com>
Cc: Greg KH <greg@kroah.com>
Cc: Jiri Kosina <jkosina@suse.cz>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Reviewed-on: http://git-master/r/402097
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417523
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
module_init() and module_exit() replace module_hid_driver().
module_hid_driver() is not applicable on kernel 3.4
Bug 1466757
Change-Id: I29e6600f1b32b406bc23c628c4ddb0b278f3daa2
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/401212
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417522
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
The low-level driver can read the report descriptor, but it cannot
determine driver-specific changes to it. The hid core can fixup
and parse the report descriptor during driver attach, but does
not have direct access to the descriptor when doing so.
To be able to handle attach/detach of hid drivers properly,
a semantic change to hid_parse_report() is needed. This function has
been used in two ways, both as descriptor reader in the ll drivers and
as a parsor in the probe of the drivers. This patch splits the usage
by introducing hid_open_report(), and modifies the hid_parse() macro
to call hid_open_report() instead. The only usage of hid_parse_report()
is then to read and store the device descriptor. As a consequence, we
can handle the report fixups automatically inside the hid core.
Signed-off-by: Henrik Rydberg <rydberg@euromail.se>
Tested-by: Nikolai Kondrashov <spbnick@gmail.com>
Tested-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
(cherry picked from commit a7197c2e4120ce40e7e3f5580336b9a1dc791220)
Change-Id: Ic94c28390c8207da74ab80895100cd076a5532f9
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/401210
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417520
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
Export hidinput_calc_abs_res to allow us to calculate
resolution in other drivers.
Only getting exporting code from
(commit id: 37cf6e6fc34e2fca4e7c565697e7cd5c317bc316)
Bug 1466757
Change-Id: Ic07922fa53f26634c3b402d669256e03c45f4789
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/401209
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417519
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
-Converted absolute coordinates to REL events.
-Adjusted blake joystick parameters to increase
granularity.
Bug 1487225
Bug 1466757
Change-Id: I3f90e79e5519a74d46947ef851b126cca4070719
Signed-off-by: Jun Yan <juyan@nvidia.com>
Reviewed-on: http://git-master/r/394924
(cherry picked from commit ed1bc9b9e6f5d38476ba97f10102b602c9b92aac)
Reviewed-on: http://git-master/r/401208
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417518
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
In order to customize the flat and fuzz of the
joystick, create an separate hid driver for
Shield joystick. It does the same hid mapping
with hid-input.c but only changes the flat and
fuzz configurations.
Bug 1352488
Bug 1466757
Change-Id: Ide6d37eeeffac9a7150fb257d30f348599794c4c
Signed-off-by: Jun Yan <juyan@nvidia.com>
Reviewed-on: http://git-master/r/335198
(cherry picked from commit e0e74a97241af85468858cdd79fd4ba994804007)
Reviewed-on: http://git-master/r/401207
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417517
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
add notifier function to remove p2p netdevice binding on
NETDEV_DOWN or NETDEV_UNREGISTER events
Bug 1478118
Bug 1470921
Bug 1466757
Change-Id: I6a18c65ee45affeaa6f459b656888c1c52d2fd3b
Signed-off-by: bibhayr <bibhayr@nvidia.com>
Reviewed-on: http://git-master/r/368141
(cherry picked from commit 28d61853e7f35e80ba11784eceb83acd1a870fac)
Reviewed-on: http://git-master/r/401206
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417516
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
Make sure we remove node from list while we still
hold lock.
Bug 1474422
Bug 1466757
Change-Id: I7e23f6432f347937b1883ea086e55f5c324fc985
Signed-off-by: Rupesh Gujare <rupesh.gujare@atmel.com>
Signed-off-by: Vinayak Pane <vpane@nvidia.com>
Reviewed-on: http://git-master/r/380497
(cherry picked from commit 466f6ed30787d16fff3f74e9412416de5b1eb0f6)
Reviewed-on: http://git-master/r/401205
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417515
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
Update to driver version 10.00.01.02.05
Bug 1459299
Bug 1466757
Change-Id: I73dcbb97093179c4a69b9e5cbfc4d10a16e228ec
Signed-off-by: Vinayak Pane <vpane@nvidia.com>
Reviewed-on: http://git-master/r/368040
(cherry picked from commit aaa4d5c3e5e21b3a220b3103b72eee6fda0203b3)
Reviewed-on: http://git-master/r/401204
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417514
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
Update from ATMEL to send an event to userspace to
indicate that a device has entered or resumed from
sleep.
Bug 1394137.
Bug 1421799.
Bug 1466757
Change-Id: I25b02bd8ae8a01a52d28b8254fbc43401c0f9463
Signed-off-by: Todd Poynter <tpoynter@nvidia.com>
Reviewed-on: http://git-master/r/355592
(cherry picked from commit d211697344d461651fd0324cce2297f71252df7c)
Reviewed-on: http://git-master/r/401203
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417513
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
Comes from 'Merge tag v3.10.24 into HEAD'
The files are copied and removed manually base on main
Bug 1466757
Change-Id: I413d0dcc6d5d9855a853db4e03b9c6ae1c40b5e9
Reviewed-on: http://git-master/r/401201
Signed-off-by: Kenneth Kwak <kkwak@nvidia.com>
Reviewed-on: http://git-master/r/417511
Reviewed-by: Peter Kim <pekim@nvidia.com>
Tested-by: Peter Kim <pekim@nvidia.com>
|
|
Discrediting all the UI's from either end that are less than 30%
of the estimated UI.
Not using a discredited UI for any comparisons. If one of the UIs
in a comparison is already discredited, discrediting the other UI
as well.
Checking for multiple holes in the same window.
For margin calculations for window ends identified as tap holes, use
n'th Vmin hole for n'th Vmax hole position.
Bug 1423423
Change-Id: I7bebfbc1422f2da722e8415f942488d7b17f828d
Signed-off-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-on: http://git-master/r/368867
(cherry picked from commit fda601e6a4c50b3004cee7d8f016706bd21cee6c)
Reviewed-on: http://git-master/r/415583
Reviewed-by: Harry Hong <hhong@nvidia.com>
Tested-by: Harry Hong <hhong@nvidia.com>
|
|
For devices that are always powered on, run calibration in
platform resume. The resume path for these devices primarily
restores host context and doesn't call any signal voltage
change APIs. This patch ensures that calibration is done
during resume and proper drive strength codes are applied.
Bug 1423423
Change-Id: Iaae2fba42395a2b783bcac06e3141842340c4e50
Signed-off-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-on: http://git-master/r/387819
(cherry picked from commit 901b27722af774588865012bd85505f365dca8f1)
Reviewed-on: http://git-master/r/415582
Reviewed-by: Harry Hong <hhong@nvidia.com>
Tested-by: Harry Hong <hhong@nvidia.com>
|
|
For negative margin calculations, use the first valid full window
in the first valid UI if Avg UI is found.
If Avg UI is not found, use first and second full windows to determine
the negative margin.
During negative margin calculation, marking each step as boundary.
Bug 1423423
Change-Id: I5c79a890799c442b1e6be5243db362a03efc58bc
Signed-off-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-on: http://git-master/r/362768
(cherry picked from commit 976bfae7bf33dd5fe2bc653627df44d8f2688a21)
Reviewed-on: http://git-master/r/415581
Reviewed-by: Harry Hong <hhong@nvidia.com>
Tested-by: Harry Hong <hhong@nvidia.com>
|
|
Modifying the negative margin additions to partial window start
as per the new corner case identified by characterization team.
In case where the avg ui is found, negative margins are found
using first full window start and avg ui. If the avg ui is not
found, est ui is taken as avg ui and negative margins are obtained
using avg ui and all boundary starts.
Bug 1423423
Change-Id: I762cbe7e36f72f9744ca8cd8dee3114758aa7597
Signed-off-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-on: http://git-master/r/361974
(cherry picked from commit de54e591bfcd9f9f2e0989b4284d04cb30a729c0)
Reviewed-on: http://git-master/r/415580
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Harry Hong <hhong@nvidia.com>
Tested-by: Harry Hong <hhong@nvidia.com>
|
|
With the existing clock sources, 100MHz clock freq cannot be
set for UHS SDR50 mode. The closest frequency for which tap hole
coefficients data exists is 81.6MHz. Hence, limiting SDR50 mode
clock frequency to 81.6MHz.
Bug 200006069
Change-Id: Ia942e99f241dc93788c95eccc5ebf75090bbb2c6
Signed-off-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-on: http://git-master/r/415137
Tested-by: Harry Hong <hhong@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Harry Hong <hhong@nvidia.com>
|