mirror of
https://github.com/Evolution-X/hardware_interfaces
synced 2026-02-01 11:36:00 +00:00
0f56c5670985cd43b27f7487da9213fbd5729416
The camera HAL may signal release fence after processCaptureResult. If the VTS test waits for the release fence in the context of the capture result, there is possibility of deadlock. Rather, we should wait for the releaseFence in a different thread context to really emulate the real application behavior. Test: atest VtsAidlHalCameraProvider_TargetTest Bug: 241281568 Change-Id: Id1d92e901aae1cab084846d252ef090fcda182d7
Merge "Adding bluetooth apex and min_sdk_version" am:
85d3fae9c5 am: 9793b79ce7 am: 08e6905ff5 am: 9b8d57f1b8
Merge "Fix tunerhal vts feId uninitialized on getFrontendIdByType" into android11-tests-dev am:
40087f64c5
Merge "Build with upstream lld: Fix incorrect static dependencies" am:
9f18cbd7f6 am: 67a2c6d6f1 am: 8fea839883
Description
No description provided
Languages
C++
56.3%
AIDL
41.2%
C
1.5%
Rust
0.4%
Java
0.4%
Other
0.1%