Age | Commit message (Collapse) | Author |
|
In Tegra Profiler misc driver, do not expose kernel-space IPs
for security purposes.
Bug 1312406
Bug 1349673
Change-Id: I07f1ee2036b62dbf7195f3fac4f9632f07933616
Signed-off-by: Andrey Trachenko <atrachenko@nvidia.com>
Reviewed-on: http://git-master/r/262013
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Daniel Horowitz <dhorowitz@nvidia.com>
Tested-by: Daniel Horowitz <dhorowitz@nvidia.com>
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
GVS: Gerrit_Virtual_Submit
|
|
check_vma_address function:
sometimes (rarely): address value may be overflowed.
Bug 1312406
Change-Id: I2073c264e78013591ddb343763f60ba920e04b90
Signed-off-by: Igor Nabirushkin <inabirushkin@nvidia.com>
Reviewed-on: http://git-master/r/258228
Reviewed-by: Andrey Trachenko <atrachenko@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
Tested-by: Andrey Trachenko <atrachenko@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Bo Yan <byan@nvidia.com>
|
|
NV_ENABLE_CPU_BOOST was enabled based on ENABLE_AUTO_SCAN. Raydium
v55 drop removed ENABLE_AUTO_SCAN macro, that caused cpu boosting
logic to be always disabled. Re-enable cpu boosting code.
Bug 1306792
Change-Id: Ic4dcbaa515b1c09b46fc095fb651984e37b80785
Signed-off-by: Yogish Kulkarni <yogishk@nvidia.com>
Reviewed-on: http://git-master/r/238403
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
channel 165 is not the side band of 40MHz 5G channel
Bug 1298751
Change-Id: I9f29d11d30b1394ab097c82f97b177acd98149a2
Signed-off-by: bibhayr <bibhayr@nvidia.com>
Reviewed-on: http://git-master/r/240198
(cherry picked from commit 95e0bfd5949e8bcfb2513a06bd0467d94fe84a92)
Reviewed-on: http://git-master/r/257889
GVS: Gerrit_Virtual_Submit
Tested-by: Narayan Reddy <narayanr@nvidia.com>
Reviewed-by: Narayan Reddy <narayanr@nvidia.com>
Reviewed-by: Thomas J. Meier <tmeier@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Rakesh Kumar <krakesh@nvidia.com>
|
|
Add Tegra Profiler kernel misc driver
Bug 1312406
Change-Id: I40950c0c82a22d3a7abd99e10cb7793644c6293e
Signed-off-by: Igor Nabirushkin <inabirushkin@nvidia.com>
Reviewed-on: http://git-master/r/255723
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Andrey Trachenko <atrachenko@nvidia.com>
Tested-by: Andrey Trachenko <atrachenko@nvidia.com>
Reviewed-by: Maria Bornski <mbornski@nvidia.com>
|
|
Enable Tegra profiler for Tegra platforms
Bug 1312406
Change-Id: I01785a321ebf1be1c998eea6ebd0e255dad5e1a7
Signed-off-by: Igor Nabirushkin <inabirushkin@nvidia.com>
Reviewed-on: http://git-master/r/255729
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Andrey Trachenko <atrachenko@nvidia.com>
Tested-by: Andrey Trachenko <atrachenko@nvidia.com>
Reviewed-by: Maria Bornski <mbornski@nvidia.com>
|
|
Fix incorrect changes in the arch_arm_kprobe
function (commit: 3b3f4d24917c97fa75aa4fba2b09797ef94cea38)
Bug 1228659
Change-Id: Iff49cdf0529d42d391f911f614f54af93eb25c76
Signed-off-by: Igor Nabirushkin <inabirushkin@nvidia.com>
Reviewed-on: http://git-master/r/255718
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Andrey Trachenko <atrachenko@nvidia.com>
Tested-by: Andrey Trachenko <atrachenko@nvidia.com>
Reviewed-by: Maria Bornski <mbornski@nvidia.com>
|
|
These two routines use semaphore to protect pwm resource.
However they can be called via led timer ISR, thus causing
linux BUG. Remove the call to these two functions and use
pwm_config instead
Bug 1333079
Change-Id: I6db788218f74c030956272ee0fcb9c7ec8a0652f
Signed-off-by: Jun Yan <juyan@nvidia.com>
Reviewed-on: http://git-master/r/253619
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Tao Xie <txie@nvidia.com>
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
This change fixes abnormal signal handling in tf driver.
Tf_daemon(user thread) is waiting for the signal when coming out of LP0,
but tf_daemon never gets the signal because tf driver can't handle the
signal properly. If there's a pending signal when coming out of LP0,
this fix clears the pending signal.
Bug 1244750
Bug 1309812
Change-Id: I7849866c7993af8716c17f6b7a06692271334664
Signed-off-by: Hyung Taek Ryoo <hryoo@nvidia.com>
Reviewed-on: http://git-master/r/253586
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Jun Yan <juyan@nvidia.com>
Tested-by: Jun Yan <juyan@nvidia.com>
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
This reverts commit 8067f19868040be42e53bb05778138502c899632.
Change-Id: I6bf285be6a0ff3657d33bc3ecc99544cd4f83344
Signed-off-by: Jun Yan <juyan@nvidia.com>
Reviewed-on: http://git-master/r/253585
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
Ensure OOB interrupt is always registered when bus is active.
Fixes this bug:
If there was an SDIO error during the initial firmware download,
the OOB interrupt will not get registered. Then, on subsequent
device resets, the code for registering OOB interrupt did not
get called again - causing a persistent wifi failure.
Bug 1327983
Change-Id: Ie0bca0a1ae757074140cc78e9b7c44175eec8581
Signed-off-by: Michael Hsu <mhsu@nvidia.com>
Reviewed-on: http://git-master/r/253016
Reviewed-by: Kyeong Kim <kyeongk@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Steve Lin <stlin@nvidia.com>
|
|
This reverts commit ac475a8eef3acc44297d4853fde82b87c31dda2b.
Change-Id: I07d9672f3eadbdeebd85829480597661ce5259f5
Signed-off-by: Jun Yan <juyan@nvidia.com>
Reviewed-on: http://git-master/r/253114
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
|
|
Tuning at 1.39V to find a valid tap value that works at all core
voltages.
Boosting emc clock to 900MHz before setting 1.39V and releasing the
frequency after 1.39V setting is removed.
Bug 1331018
Change-Id: Icbf009a90ba9d0bd88a5991aab2fad8f1783b823
Signed-off-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-on: http://git-master/r/252471
Tested-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
GVS: Gerrit_Virtual_Submit
|
|
Limiting SD card clock to 82MHz to ensure that the tap values
obtained through tuning work with the full core voltage range
even with boost mode enabled
Change-Id: I562bb651d8eca8d412ea464cfbdca1b692783e55
Signed-off-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-on: http://git-master/r/252371
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Venu Byravarasu <vbyravarasu@nvidia.com>
GVS: Gerrit_Virtual_Submit
|
|
Even if nominal_vcore_tun_done, override_vcore_tun_done are set
don't skip tuning for 2nd core voltage.
Bug 1330031
Reviewed-on: http://git-master/r/242764
(cherry picked from commit 57b7008d0ad3cfdea888416e8b1db3ebb0c7cda7)
Signed-off-by: Naveen Kumar Arepalli <naveenk@nvidia.com>
Change-Id: I0a90a9d317bd46558eaa9112391c33cc867b247e
Reviewed-on: http://git-master/r/251897
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-by: Venu Byravarasu <vbyravarasu@nvidia.com>
|
|
K3.4 does not need this code maintain to PF_KTHREAD
Bug 1244750
Change-Id: Iec2fdf2cf4646ea3415f370a45376b1757498854
Signed-off-by: Hyung Taek Ryoo <hryoo@nvidia.com>
Reviewed-on: http://git-master/r/251113
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
Tested-by: Peter Zu <pzu@nvidia.com>
|
|
This change creates a sysfs node
/sys/bus/platform/devices/palmas-pmic/auto_smps45_ctrl
echo 1 : force multi phase mode
echo 0: auto phase selection
Bug 1323712
Change-Id: Ibbac78cf841b1cda3444ad388426a0da4a67c38a
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/251057
GVS: Gerrit_Virtual_Submit
Tested-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
|
|
Change-Id: I25851ce78f034ac592a0bd39ded1444f0a7e230d
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/251056
GVS: Gerrit_Virtual_Submit
Tested-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
|
|
Sysfs for changing tap value for wifi
Change-Id: I08e0971c562cf1e491373173d5b3b7e5af1da6ba
Signed-off-by: Naveen Kumar Arepalli <naveenk@nvidia.com>
Reviewed-on: http://git-master/r/250897
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Matt Wagner <mwagner@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
|
|
Change-Id: Ia3f1f5d1eb13944ec66db335abc29350a22da3df
Signed-off-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
Reviewed-on: http://git-master/r/250896
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
Change-Id: Ia8bf319da85914e748c4a88877433e6c45667ef1
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/250565
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
Added mechanism to install sysfs objects for tegra shared bus floors.
Currently no floor objects are installed.
Change-Id: I20e1a1448ee799a5ec59087f3214b77a80c05408
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/250564
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
Add cap, floor, and override shared users to host1x bus. Attached cap
user to core cap interface.
Change-Id: I20bf5f346f422d7f2cbd97a445f00847e8761ac8
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/250563
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
- Set host1x dev_id = "host1x" and con_id = NULL (these definitions
were used before conversion of host1x to shared bus; during conversion
ids were inadvertently swapped - restored now)
- Renamed host1x bus shared users to be consistent with other shared
buses
Change-Id: Iecf1f27681658c69fc63ed71c99d62ae86d9f30b
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/250562
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Anshul Jain (SW) <anshulj@nvidia.com>
Tested-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
|
|
Change-Id: Ie63f856727f9ba9f93e6c75b7bd5fb80357448a4
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/250561
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
|
|
- Allowed per-SoC code to select emc monitor preset rate.
For now, rounded down boot rate is used as monitor preset rate
(round down to not over-clock on boot).
- Skipped emc clock update when monitor preset rate is set, but not
yet enabled (to avoid temporary dip in EMC rate). EMC rate is updated
only when monitor preset is enabled.
- Preset EMC monitor rate after iso usage table is initialized.
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/219504
(cherry picked from commit 9279fd450cba7c8012a405755d483dfc9b502941)
Change-Id: I2b724df9dc95231d6a5760171aa18bd10bdb409a
Signed-off-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
Reviewed-on: http://git-master/r/250525
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
|
|
Use EMC boot rate as EMC monitor output reading during initialization
until actual monitoring starts.
Bug 1239168
Change-Id: I64d397623eeafe459769db106d0bfe80223f654f
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/250524
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
|
|
Change-Id: Iea43edd693d1489aa87eff893a1cfcfca1379552
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/250523
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
|
|
Added fine granularity region to cbus possible rates. In this region
requested cbus rate is not clipped to dvfs steps, but rounded to fine
granularity resolution. The latter is set as 12MHz, and the region is
defined as 5 resolution steps below the top dvfs rate, assuming this
top rate is reachable on the particular chip bin/sku.
Change-Id: If1096ae068367819e64c55172c1a1c0a46c38b86
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/250033
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
|
|
Updated dvfs and edp tables, clock and voltage limits for T40T part.
Change-Id: Ic256a6f3aa8026c96443ecc33204309275fcbe2e
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/250032
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
|
|
Change-Id: Id5c2163224cdb1c862ef708e0790d99e4f04775e
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/250031
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
|
|
On T40T parts removed throttling of nominal voltage by boot core edp.
Used the latter to specify detached mode (boot, disable, suspend)
limits.
Change-Id: Ifa846ec8c7cb79df91b80cc81ffdef0f02a45372
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/250030
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
|
|
DVFS rail nominal voltage is minimum voltage required to run all
associated clocks at maximum allowed rates. DVFS rail can be detached
from clocks during initial boot, on suspend entry/exit, or when
voltage scaling is disabled. So far, rail voltage in any detached mode
was set to nominal level. This commit introduced separate voltages for
each detached mode. If any of these levels is not specified, backward
compatible nominal voltage is used.
Since, suspend voltage may now be different from nominal (below), it
is important for dvfs to suspend after suspend edp rate caps are set,
and resume before edp. Hence, priorities of dvfs suspend notifiers
were adjusted accordingly.
Change-Id: Id05e0b16f24dc7d28b1ee9e87afd63d98a9ab86e
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/250029
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Xiao Bo Zhao <xiaoboz@nvidia.com>
|
|
Bug 1315200
Change-Id: If1bfc2a17d302f10b4d5439fa5e1ba5914b2fcc5
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/244113
Reviewed-by: Tao Xie <txie@nvidia.com>
Tested-by: Tao Xie <txie@nvidia.com>
|
|
Call tegra_hotplug_signal to queue deferred work after a delay of 30ms and call gpio_get_value
in tegra_dc_hpd
bug 1310096
bug 1298680
Change-Id: Iab37af3258429b1e281705eb5b077be31b53b07f
Signed-off-by: sharath sarangpur <ssarangpur@nvidia.com>
Reviewed-on: http://git-master/r/241633
GVS: Gerrit_Virtual_Submit
Reviewed-by: Jon Mayo <jmayo@nvidia.com>
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
This change takes a wakelock before stating the recovery
mechanism of JS
Bug 1306389
Change-Id: I0109455647988248f1e37d5a000e1e34654e40e5
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/241103
|
|
This change recovery the JS uC after USB resume failure by
unloading USB, resetting uC from ISSP and then reloading USB
Bug 1306389
Change-Id: I086636d4b7b91e3a2874f584fa6efbfd2cae6014
Signed-off-by: Michael Hsu <mhsu@nvidia.com>
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/240004
|
|
Unbalanced irq_enable/disable will cause potential risk of the sensor
data not being sent out. Add critical section and flag to prevent
this situation.
Change-Id: I4a8b3ebfd07b3e4901ad807c8052c38e3f23315e
Signed-off-by: Xiaohui Tao <xtao@nvidia.com>
Reviewed-on: http://git-master/r/239385
Reviewed-by: Sang-Hun Lee <sanlee@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Robert Collins <rcollins@nvidia.com>
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
Change DEF_ACCEL_ST_SHIFT_DELTA and DEF_GYRO_CT_SHIFT_DELTA to
500.
Change-Id: Id4db11789d561dfc3899d8de592421f04dbf19db
Signed-off-by: Xiaohui Tao <xtao@nvidia.com>
Reviewed-on: http://git-master/r/239833
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Robert Collins <rcollins@nvidia.com>
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
Change-Id: I342d1f1505caedabaefa0b2f0eb5dccdf5046bca
Signed-off-by: Jean Huang <jeanh@nvidia.com>
Reviewed-on: http://git-master/r/239022
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Tao Xie <txie@nvidia.com>
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
|
|
This is a WAR to reset the USB device if the device
fails to resume. We assume that the resume failure is
because of the uC hang.
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Change-Id: I6fc85cd0ce2fad7a7dbff5b6ddee0a96149a5d76
Reviewed-on: http://git-master/r/239086
GVS: Gerrit_Virtual_Submit
Reviewed-by: Tao Xie <txie@nvidia.com>
Tested-by: Tao Xie <txie@nvidia.com>
Reviewed-by: Ankit Pashiney <apashiney@nvidia.com>
|
|
v58->v59:
- Keep uC USB buffer unchanged for about 1 second when exiting suspend
mode, in order to fix false wakeup events issue
Change-Id: I175bb0328af1840cbfe8c70e0607d7d8023e0c26
Signed-off-by: Jun Yan <juyan@nvidia.com>
Reviewed-on: http://git-master/r/239099
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Tao Xie <txie@nvidia.com>
Reviewed-by: Ankit Pashiney <apashiney@nvidia.com>
|
|
Use mutexes to prevent concurrent wifi / bluetooth turn
on sequence.
Bug 1302412
Change-Id: Icd086b616af2f5ccbff7968d613310c365ad549a
Signed-off-by: Michael Hsu <mhsu@nvidia.com>
Reviewed-on: http://git-master/r/236533
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
Change-Id: I2158918b6a22a4ceeadecdfa5a51fc87a624a105
Signed-off-by: Matt Wagner <mwagner@nvidia.com>
Reviewed-on: http://git-master/r/235510
Reviewed-by: Mandar Padmawar <mpadmawar@nvidia.com>
Tested-by: Mandar Padmawar <mpadmawar@nvidia.com>
|
|
On P2560 hardware only, wifi chip generates excessive wifi
activity interrupts:
- on first boot after flashing image
WAR is to mask this specific wifi activity interrupt to
prevent it from keeping application processor awake.
Bug 1299635
Change-Id: Idf0fdaf817621e3ae5e0f63864c488366dbbcaba
Signed-off-by: Michael Hsu <mhsu@nvidia.com>
Reviewed-on: http://git-master/r/235330
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
|
|
v57->v58
-changed dead band to 38
-changed cal window to 80
Bug 1266521
Change-Id: I686ef709df77ad7d29e8cee6420683ee901a73cf
Signed-off-by: Jun Yan <juyan@nvidia.com>
Reviewed-on: http://git-master/r/235156
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
v56->v57
added changes to uC FW that will check to make sure if LED PWM timer0 == Started then check the timer0 start bit and if not set
then set it to start running again.
v55->v56
- Bump revision to v0_56.
- Changed the following End Point 2 commands:
LED_UC_DRIVE- This function now does Nothing. Left it in for backwards compatibility.
(Previously this function setup the Port 1.1 pin to drive from tri-state. And also set the LED pin high (ON).)
LED_BREATHE_ON- This function now sets up port 1.1 in a drive state from tri-state and starts timer0 for the SW PWM.
LED_BREATHE_OFF- This function now sets up port 1.1 in a drive state from tri-state.
Also keeps the same logic as before stopping the SW PWM timer0 and set P1.1 LED LOW (OFF).
Bug 1266521
Change-Id: I2ef12fe6c66e03d299b0135e749498d8154f3937
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/234431
Reviewed-by: Automatic_Commit_Validation_User
|
|
Change-Id: Ib87ff58487c324124987a563fc0621d8f8482784
Signed-off-by: Matt Wagner <mwagner@nvidia.com>
Reviewed-on: http://git-master/r/234417
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Tao Xie <txie@nvidia.com>
Tested-by: Tao Xie <txie@nvidia.com>
|
|
- Bump revsion to v0_55.
- Center point calibration window (power on/reset) now 40 from 80
- power on defaults for Right/Left Joystick X,Y axes are now 250 from150.
Note: doing this makes the scaling values less granular or smaller steps on power on.
Thus helps with RS mouse drift being a larger value just outside the center dead band.
Noticed that the RS mouse drift can go away after moving the joysticks to its max and min points.
- power on defaults for right/left analog triggers are now 600 and 300 max/min.
The original version had this at 300 and 700 reversed. Hence, on the very first trigger pull,
you only had to move a very small distance to hit max.
NOTE: Center point stiction dead band is still set to 37. Same as v52.
Bug 1266521
Change-Id: I071c9b1ef2cb837787fd4f21f0e4a6bee9aafc01
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/233806
Reviewed-by: Automatic_Commit_Validation_User
|
|
Improve headphone jack detection in certain
scenarios.
Bug 1296602
Change-Id: I748f7649680ad60edbc450c09027cb3b76552f8c
Signed-off-by: Scott Peterson <speterson@nvidia.com>
Reviewed-on: http://git-master/r/233081
Reviewed-by: Vinod Subbarayalu <vsubbarayalu@nvidia.com>
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
|