Age | Commit message (Collapse) | Author |
|
* Other devices including this repo will have conflicts
Change-Id: I0e0f3fc6854a0a898f074660163f6bd9e39cfb87
Signed-off-by: electimon <electimon@gmail.com>
|
|
* We can't make use of most of the debug features on userdebug builds.
Change-Id: I31df2090b31243b742c4e82dc08cd8491dada54f
|
|
tm-qpr3-release
Change-Id: Ie9d3c5c330b2e7eed6ceda5e810d248ca350606b
|
|
|
|
tm-qpr3-release
Change-Id: If317b636816fcfc4a6afb7cde12713f864d5dc60
|
|
* changes:
ADPF: send ADPF_FIRST_FRAME hint
ADPF: support sending power hint
|
|
To send ADPF_FIRST_FRAME hint when reportWorkDurations was called first
time after stale state.
Bug: 243025173
Test: PtsUiBench & CUJ
Change-Id: I4377b1f549646bcf44bdf26b2657b7bc0646f9a4
Merged-In: I4377b1f549646bcf44bdf26b2657b7bc0646f9a4
|
|
Send a hint only when the system can support the hint.
Bug: 243025173
Test: PtsUiBench & CUJ
Change-Id: If56d0c22f8dd61f5fe27ba79f08f2963269abe41
Merged-In: If56d0c22f8dd61f5fe27ba79f08f2963269abe41
|
|
The throttle/release step check will be bypassed if the sensor has no
binded power rail or the power data is still collecting. Fix this issue with adding a check.
Bug: 269730273
Test: verified by emul_temp
Change-Id: I79ce02fa589a79bbe2dd0983c86099f36acd3c06
|
|
tm-qpr3-release
Change-Id: Ieeb1924577f5ae4d51de7e4a96cf322868512759
|
|
If we remove the delay time in the erase function, under back-to-back
fast typing scenario, FW would still has the chance to enter a unknown
situation and the erase function will be losed forever.
Bug: 266331748
Test: all current haptic testing and manually four fingers typing
This reverts commit db2f13d19fe68a77ec9f1c1584a222dfa2c9e0c7.
Change-Id: I4929300ad5b1927531cb89e7980f1aeace5980ff
|
|
tm-qpr3-release
Change-Id: I419aaaa7e26d72797fe5994ebff5211060477404
|
|
|
|
Currently, monitorffs will pull up gadget when the ffs
endpoints are ready. When the device change the data
role from peripheral to host, the pullup behavior will
still occur. It will cause the host mode and peripheral
mode start in the same time.
This patch will check typec and USB gadget state before
pulling up gadget.
Bug: 263435622
Bug: 266635426
Test: verified pass
Change-Id: Ibd8d3c3c34b91657327903e1063351448722e41c
Merged-In: Ibd8d3c3c34b91657327903e1063351448722e41c
Signed-off-by: Ray Chi <raychi@google.com>
(cherry picked from commit 502013d5347849aa9a2ec95d114998c22b646b17)
|
|
tm-qpr3-release
Change-Id: I478ddcac47fceecfa3b33b95b75f370e5c02bfb7
|
|
tm-qpr-dev
|
|
tm-qpr3-release
Change-Id: I05084e63c6940b4e7d104c1d4d1e6d85e9f2532c
|
|
For long irq atom and resume latency atom, we skip upload if device UART
enabled.
Test: To see if uart enable
adb shell getprop | grep init
To verify if atom uploading data
adb shell cmd stats print-stats | grep 105043
Bug: 266465677
Change-Id: I32c9fd9ffeecb33fd35ab181d19f400518a7f743
Signed-off-by: Ziyi Cui <ziyic@google.com>
|
|
eldar/887079995
Test: adb logcat "pixelstats-vendor:D *:S"
Bug: 264287533
Change-Id: Icaa15b264fbf2f0a368411c5125fd9984cc76f66
Merged-In: Icaa15b264fbf2f0a368411c5125fd9984cc76f66
Signed-off-by: Doug Zobel <zobel@google.com>
|
|
tm-qpr3-release
Change-Id: Iaf948ba824e0b15b8a4261e6979531db673611cc
|
|
Replacing the infinite vibe_state checking to prevent the abnormal non-stop
symptom which would cause HAL stuck on the checking step.
Even if there is a vibration currently playing, we should stop
the current vibration and play the new one.
We can assume this because the Framework will handle
all the prioritization of requests before invoking HAL APIs.
Bug: 250074997
Test: Use previous non-stop FW to test it
Change-Id: I5dfc0cd4eb581d4db23094e9c73ce8e08ad85ea6
|
|
tm-qpr3-release
Change-Id: I49ed959256152e17a7295ad57c5491bb3efa78d9
|
|
tm-qpr-dev
|
|
Bug: 253366496
Test: wifi_diagnostic binary is available
Change-Id: I24c530df17def7dc4e6fa2922fa0e51d27436cde
|
|
* changes:
cs40l26: Prevent waveform number out of range
cs40l26: Improve the performance for primitive effects
|
|
sensor_status_map will not be initilized when the
vendor.disable.thermal.control debug property is enabled,
so add a check to prevent crashing if someone access
sensor_status_map.
Bug: 254163925
Test: swithc vendor.disable.thermal.control and check no thermalHAL crash
Change-Id: I6014ccdb974c1620a41df8ae32c612ff861514ca
|
|
Bug: 254163925
Test: emul_temp and verify the sensor log
Change-Id: Ia6eb5d153abae5324b8cd2eb3dd1204441e0a073
|
|
Bug: 262585499
Test: Tested on Raven, stop/start vendor.power-hal-aidl and verified thermal power hint
by emul_temp
Change-Id: I1de70f05e0eb0ae4b0b2950273c437835c3fc4be
|
|
When we call the cancel vibration right after
a long compose effect, the erase command will timeout and
the active ID was set to -1.
After the effect finished, we will based on the active ID do
the erase function if it's not -1.
So, there is a chance that the active ID is -1 and the compose effect
was not erased, which will also cause an error when testing the VTS.
To fix this, I add this patch to solve this problem.
Bug: 261832151
Test: atest VtsHalVibratorTargetTest
Change-Id: I63a8455962061edce2a9615084aac6e481c91012
Signed-off-by: Chase Wu <chasewu@google.com>
|
|
When we call eraseOwtEffect() in HAL, the ff core will call kernel stop()
before calling the cs40l26_erase_owt() and it will wait for the SVC
waveform protecting time every time.
Under our use case, the vibrator should under stop status before we call
the eraseOwtEffect(). So, in eraseOwtEffect(), we turn off this protecting
time before we do the EVIOCRMFF and turn on it at the end of the
eraseOwtEffect().
Bug: 261687849
Test: atest PtsVibratorHalTestSuite \
PtsHapticsTestCases \
VibratorHalCs40l26TestSuite \
VtsHalVibratorManagerTargetTest \
VtsHalVibratorTargetTest \
android.os.cts.VibratorTest \
android.os.cts.VibratorManagerTest \
android.os.cts.VibrationEffectTest \
android.os.cts.VibrationAttributesTest \
android.os.cts.CombinedVibrationTest \
Change-Id: I48a2ad30dfb7069955ca8e5139756d0e3390fd29
Signed-off-by: Chase Wu <chasewu@google.com>
|
|
Bug: 262585499
Test: stop/start vendor.power-hal-aidl and verified thermal power hint
by emul_temp
Change-Id: I6dfc0a3d7f6ef0c39a464f5952bb447db73c20d8
|
|
* changes:
pixelatom: add atom for resume latency metrics
pixelatom: implement atom log function for long irq atom
Add VendorLongIRQStatsReported atom
|
|
|
|
|
|
Add pixel atom for resume latency metrics
Bug: 227809911
Bug: 232541623
Test: Verified the existence of atom and correctness of atom stats
adb shell
cmd stats print-logs && logcat -b all | grep -i 105044
Signed-off-by: Ziyi Cui <ziyic@google.com>
Change-Id: Id1de281a6432d75085e70af50299d687e2238e08
(cherry picked from commit 716ffa3025e70210d82a3e9fe6ba01fb81c5fe09)
|
|
Implement log function for long irq metrics atom
Bug: 227809911
Bug: 232541623
Test: Verified the existence of atom and correctness of atom stats
adb shell
cmd stats print-logs && logcat -b all | grep -i 105043
Signed-off-by: Ziyi Cui <ziyic@google.com>
Merged-In: I2fffd36772dda1e590a09f8d8fcaf3164f74aafb
Change-Id: I2fffd36772dda1e590a09f8d8fcaf3164f74aafb
(cherry picked from commit 10613eb0db34072c38078d4fb73a3f1e979d24af)
|
|
Bug: 227809911
Bug: 248354974
Test: Tested long irq atom
Merged-In: I22ef9e68dc9c27d6078245d03a47376136d2d059
Change-Id: I22ef9e68dc9c27d6078245d03a47376136d2d059
(cherry picked from commit 1199a637191771ce214fc92b6556e5206fe5dbe1)
|
|
Add pixel atom for temperature residency metrics
Bug: 246799997
Test: Verified the existence of atom and correctness of atom stats
adb shell
cmd stats print-logs && logcat -b all | grep -i 105045
Signed-off-by: Ziyi Cui <ziyic@google.com>
Merged-In: I903296163b3f6a5d753a1ce1adca3af1ba8185c1
Change-Id: I903296163b3f6a5d753a1ce1adca3af1ba8185c1
|
|
Some products have the speaker numbers more than two.
To cover atom report stats of VendorSpeakerStatsReported.
Bug: 248451580
Test: manually tested passed and logcat verified
Change-Id: Ia12b873663bd000db276e4a047e6e0538db45725
Signed-off-by: Roger Fang <rogerfang@google.com>
|
|
|
|
Bug: 258188795
Test: capture trace from traceur and able to see CMA traces
Change-Id: I0f8ce176f0d14d94dc69571d5bbd5174733c253e
Signed-off-by: Martin Liu <liumartin@google.com>
|
|
Add traces for temperatures, PI parameters and cdev votes
Bug: 230664512
Test: Build and boot on device. Check traces for hal
adb shell atrace --stream hal > trace.txt
Change-Id: I6070346bd21bbb5d07ff151ca1aea718cd889cf0
Signed-off-by: Sayanna Chandula <sayanna@google.com>
|
|
|
|
Create pixel speicifc trace buffer and enable CMA trace events.
At bugreport, dumpstate will dump the trace buffer into
dumpstate_board.txt
binder:3947_2-3963 [003] .... 29.954681: cma_alloc_start: name=vframe count=16 align=4
binder:3947_2-3963 [003] .... 29.956230: cma_alloc_finish: name=vframe pfn=946080 page=000000003d6b380b count=16 align=4
binder:3947_2-3963 [003] .... 29.956235: cma_alloc_info: name=vframe pfn=0x946080 count=16 align=4 nr_migrated=16 nr_reclaimed=0 nr_mapped=16 err_iso=0 err_mig=0 err_test=0
binder:3947_2-3963 [003] .... 29.988325: cma_release: name=vframe pfn=946080 page=000000003d6b380b count=16
It's useful to investigate CMA allocation problems.
Test: "adb bugreport" includes the trace dump in dumpstate_board.txt
Bug: 238728493
Change-Id: I5eb2f79152d32ff7dbb4b9a7ea679facb186aa00
Signed-off-by: Minchan Kim <minchan@google.com>
|
|
|
|
Bug: 235378836
Change-Id: Ic68e4e9d0549d4866c29b0180445cae26b817a2c
Signed-off-by: Jenny Ho <hsiufangho@google.com>
|
|
Add cca rates of VendorAudioHardwareStatsReported
Atest cmd:
atest PixelAtomsTest:com.google.pixelatoms.PixelAtomsTest#testVendorPushedAtomsHasReverseDomainName
Bug: 249225148
Test: check log in logcat & ATEST manually
Change-Id: Ic2572439c889cab499cfb5477de7503723e9f083
Signed-off-by: Roger Fang <rogerfang@google.com>
|
|
The main problem is the timer thread could be woken after the session
was destroyed. We did have a closed flag which was set in destructor and the flag would be checked before handleMessage accessing the session
instance. To fix the problem, the operations of flag checking and session instance accessing should be guarded by the lock.
Bug: 236674672
Test: manual test
Change-Id: I49a18efbc135b1bc070b101038a8a0bcc6e19fec
|
|
|
|
Add some basic control logic into libperfmgr to disable or enable certain actions.
"EnableProperty" can be set by external process or internally by PropertyNode, if
not assigned or set, action is enabled by default.
Bug: 241054358
Test: /data/nativetest64/libperfmgr_test/libperfmgr_test
Signed-off-by: Wei Wang <wvw@google.com>
Change-Id: I5742bb901492f2675c5c88d9b09c1072ded8432a
|