| Age | Commit message (Collapse) | Author |
|---|
|
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: Tao Xie <txie@nvidia.com>
Reviewed-by: Ankit Pashiney <apashiney@nvidia.com>
(cherry picked from commit 775f7c0f628c42e6fefd43e4990cf809d80c76c2)
Reviewed-on: http://git-master/r/247439
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Diwakar Tundlam <dtundlam@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: Anshul Jain (SW) <anshulj@nvidia.com>
(cherry picked from commit eda52401485aeef531413df54af126e610612fa0)
Reviewed-on: http://git-master/r/247438
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Diwakar Tundlam <dtundlam@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
(cherry picked from commit d110f0290bcd5870abcda7b97affbe2b5d585045)
Reviewed-on: http://git-master/r/246790
Reviewed-by: Jun Yan <juyan@nvidia.com>
Tested-by: Jun Yan <juyan@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Diwakar Tundlam <dtundlam@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
(cherry picked from commit 6b3694714c6799624c45103cc0aca42e6a697e27)
Reviewed-on: http://git-master/r/246789
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Jun Yan <juyan@nvidia.com>
Tested-by: Jun Yan <juyan@nvidia.com>
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
|
|
v51->v52
- Bump revsion to v0_52.
- All Joystick Wakeup out of Suspend Tuning changes:
- Added a ADC Channel Synchronizer so as to make the Left and right joystick axes has a higher suspend mid point value.
This helps the sensitivity when moving the POT towards the GND node.
- Because of the ADC channels Sychronizer the Left and Right Analog triggers needed more Threshold tuning:
now Left Analog Trigger threshold is < 100 (was 150) and Right Analog Trigger Threshold is > 350 (was 375)
This helped move the wakeup trigger point more away from the ends.
- For the Left and Right Joysticks; we added two Thresholds wakeup methods:
1) the original dADC/dt with a delta threshold of 80. same as v46.
2) a "Measured" suspend MID-point min and max threshold.
This helps wake up when user move joystick slowly to one side or the other.
Measured absolute Thresholds are set to suspend mid point- 150 and + 150.
If suspend mid-point is too low then we will default to a low threhold of 85.
v46->v51
- Bump revsion to v0_51. This has everything that v46 has.
- Has joystick wakeup and Left and Right Analog trigger wake up.
- Analog triggers use a fixed absolute threshold: Left is set to < 150 and Right is set to > 375
- The Left and Right Joysticks still are using dADC/dt methodolgy with a threshold of 80.
However, it can be a little difficult to wake up using these. Especally if the using moves towards GND side of the POT.
Bug 1266521
Change-Id: I2322d0265fac69314368d025656e3fef8d3be414
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
(cherry picked from commit 9d0f6ae86de61f3360932b1598e8da18b0fe7404)
Reviewed-on: http://git-master/r/229465
(cherry picked from commit b5807e7f8414aac1763d66f811c70b817d7cdb28)
Reviewed-on: http://git-master/r/246787
Reviewed-by: Jun Yan <juyan@nvidia.com>
Tested-by: Jun Yan <juyan@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
|
|
v40->v46
- Removed Debug GPIO P3.0
- No wakeup pulse sent in OS Idle/Display Off (aka Active/LED Breathing ON)
- If LED Breathing remains ON when Display is ON, will turn off LED
Breathing with button press or Joystick Motion (no Analog Triggers).
LED breathing on in this state is a DON’T care because Tegra is
overriding the LED control.
- Added back Joystick wakeup during USB Suspend. Only Left
and Right Analog sticks and NO Analog Triggers.
- Suspend Joystick wakeup Threshold is set to 80.
- Added a usb activity check before the LED control logic in the suspend loop. If usb activity detected; we will bail out of the loop.
This change more matches v31 suspend loop that seems to be running LP0 suspend/resume cycles just fine.
Noticed on the scope that the timing delta relationship from Resume to T-setup requests were varying quite a lot. The LED control logic
just seems to be the reason for the large timing jitter.
- Added Port 3.0 debug toggle in the following functions:
* uC Waiting for USB enumeration packets from the Host.
* While loop LED timer0 in the beginning of Suspend; Will toggle P3.0.
- While LED timer0 ISR timeouts are still implemented.
- LED flicker fix
Bug 1276644
Bug 1285468
Bug 1266521
Bug 1283114
Change-Id: I609742ea3aae5b84a90a929bb19db0b2edd4c576
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/227147
Reviewed-on: http://git-master/r/228579
(cherry picked from commit fe7c0f0261b7f5e1cee7ee4e24265d065117828e)
Reviewed-on: http://git-master/r/246786
Reviewed-by: Jun Yan <juyan@nvidia.com>
Tested-by: Jun Yan <juyan@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
|
|
v39->v40
Updates the guard band to 37
Bug 1282562
Change-Id: Ifd2e2c9803a2af0311a4017bec878f94522085b7
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/225341
(cherry picked from commit 8d6366b0890f9268a5a843e549dbb6f944bfa33f)
Reviewed-on: http://git-master/r/246785
Reviewed-by: Jun Yan <juyan@nvidia.com>
Tested-by: Jun Yan <juyan@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
|
|
P2560 v0_38->v0_39
- Bump revsion to v0_39.
- Changed LED feed-forward table for optimal breathing cycle.
- LED Flicker fix when plugging and unplugging USB power. (aka Tegra goes into LP0 and into Idle/screen off.)
- Clear NAK counter and state when going from Suspend to active with LED_UC_DRIVE set.
- Make sure Suspend state if fully clear out of suspend; so we can respond to USB packets from tegra.
- Mure sure wakeup Puluse gets cleared when going from Suspend to active/LED_UC_DRIVE. flag was not getting cleared in active state.
- USB Descriptor name change "NVIDIA Corporation" "NVIDIA Controller v01.01"
- NAK 1 second code is still activiated.
P2454 v0_30->v0_31
- Same as v0_30 expect USB decriptor name change "NVIDIA Corporation" "NVIDIA Controller v01.01"
Bug 1266521
Change-Id: Ibc8b3bfbbc1c8f676ec4cb0e7c399346797ce653
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
(cherry picked from commit f34dac428fa5724b844bee7800c7d225f695e9ba)
Reviewed-on: http://git-master/r/246784
Reviewed-by: Jun Yan <juyan@nvidia.com>
Tested-by: Jun Yan <juyan@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
|
|
P2454
v30 change to make revision readable
P2560
v37->v38
- Bump revsion to v0_38.
- Change PID o 7203.
- change minimum PWM% to 4%.
- improve LED breathing jitter when sending wakeup pulse in active and suspend
mode.
- add LED control Feed Forward Table method to adjust the LED smoothness and
cycling time.
- adjust LED breathing behavior according to POR
- NAK 1 second code is still activiated.
Bug 1266521
Change-Id: I3514da906d1baf9d7ed159f92d1fc82c0e1796f1
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
(cherry picked from commit 3a73a3f4604f08eeb1074d5c5a59a798e3668f6a)
Reviewed-on: http://git-master/r/246783
Reviewed-by: Jun Yan <juyan@nvidia.com>
Tested-by: Jun Yan <juyan@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
|
|
This change separates issp device configuration for p2454 and
p2560 boards.
This change also downgrades the JS firmware P2454 from v37 to
v30. Also, it creates a node for p2560 with v37.
Bug 1266521
Bug 1270341
Bug 1276644
Change-Id: Ibb4b59d48146b71a8dec83c2460716299f38a0fc
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
(cherry picked from commit 98315d3198696048bdaad20ae9b069f1cf883100)
Reviewed-on: http://git-master/r/246782
Reviewed-by: Jun Yan <juyan@nvidia.com>
Tested-by: Jun Yan <juyan@nvidia.com>
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
|
