This was done in ag/22462586 internally which is too large to
cherry-pick. It's being applied to aosp to unblock some trunk stable
work.
This CL is generated with:
`m android.hardware.power.stats-freeze-api`
Test: m
Bug: 290265210
Change-Id: I385860dbd7e0d183e159353b2e2d0f8fb5b444eb
Merged-In: I832ab7a8b5445ba85e27bbcf5be64906bfa0e5be
Add people who should be listed (including the primary owner) and
remove folks who are no longer involved.
BUG: 218899982
Change-Id: I0a479e528bd436668b8782ebc123e4fdb8b4e50b
VSR requires to support power HAL V2 and beyond, this patch changes the
default implementation to reflect that.
Bug: b/253516147
Test: atest VtsHalPowerTargetTest
Change-Id: I56f6f847f4c47775db6350b8a3fcd7ee9c9cdf17
Merged-In: I56f6f847f4c47775db6350b8a3fcd7ee9c9cdf17
Per [VSR-3.2-013] DEVICEs launching with Android 13 MUST meet the
requirements for the target-level=7 compatibility_matrix file. Update
the VTS to reflect that.
Bug: b/253516147
Test: atest VtsHalPowerTargetTest
Change-Id: Ie6178ed2caea6a70b728dfcded9fa900ee099f2f
Some are still in VNDK because they are used in other VNDK libs.
Ignore-AOSP-First: some libs are still in internal master only.
Bug: 234181591
Test: m
Merged-In: If999df9c78a20df931177da11742b1c5de19bc08
Change-Id: If999df9c78a20df931177da11742b1c5de19bc08
(cherry picked from commit 5527adfd7f)
The AoC power stats reporting might not be present when the
AoC latency exceeds the allowed time after the timeout mechanism
introduced in AoC state residency data provider.
Bug: 229696611
Test: run vts -m VtsHalPowerStatsTargetTest
Change-Id: I7c59ab50065961ed338314d6c8d22d41ece43e5f
Signed-off-by: Darren Hsu <darrenhsu@google.com>
Owner information is backfilled for the following modules:
VtsHalPowerV1_1TargetTest
VtsHalPowerV1_2TargetTest
VtsHalPowerV1_3TargetTest
Each VTS module is required to have OWNERS file. The ownership is based on
go/vts-owners. For more information about ownership policy, please visit
go/xts-owners-policy.
Test: Tree Hugger
Bug: 143903671
Change-Id: Iacce57160c61adb151ca93c6e1fe2f3402b3a680
Each VTS module is required to have OWNERS file. The ownership is based on
go/vts-owners. For more information about ownership policy, please visit
go/xts-owners-policy.
Test: Tree Hugger
Bug: 143903671
Change-Id: I38023df845aae6e416508751f24dd7c8b8ec7faa
The ndk_platform backend will soon be deprecated because the ndk backend
can serve the same purpose. This is to eliminate the confusion about
having two variants (ndk and ndk_platform) for the same ndk backend.
Bug: 161456198
Test: m
Merged-In: I0652f1efe920111d79dd8c2ecd52e55dda54538f
Merged-In: Ib58c9f1cb80d083a3c62d03415610be855b80f03
Change-Id: Ied92f2784ed7d6a73693c640042c8a66fbbcfa17
The ndk_platform backend will soon be deprecated because the ndk backend
can serve the same purpose. This is to eliminate the confusion about
having two variants (ndk and ndk_platform) for the same ndk backend.
Bug: 161456198
Test: m
Merged-In: I0652f1efe920111d79dd8c2ecd52e55dda54538f
Change-Id: Ib58c9f1cb80d083a3c62d03415610be855b80f03
(cherry picked from commit c426c6dbdc)
Each VTS module is required to have OWNERS file. The ownership is based on
go/vts-owners. For more information about ownership policy, please visit
go/xts-owners-policy.
Test: Tree Hugger
Bug: 143903671
Change-Id: Ib97ced9978994e4c657de3a6ea1058dcccba5738
The ndk_platform backend will soon be deprecated because the ndk backend
can serve the same purpose. This is to eliminate the confusion about
having two variants (ndk and ndk_platform) for the same 'ndk' backend.
Bug: 161456198
Test: m
Change-Id: Ibe8beeaf0d1b33968fb782f1f70c17ae9e9bf871
Data providers that provided data for multiple entities were being added
to the data structure as nullptr due to move semantics. Now they will
only be added once (ensuring no more nullptr entries) and an index will
map each power entity id to its corresponding data provider.
Bug: 184290936
Test: Presubmit
Change-Id: I858269beb36ba5f87bb14a228079f3abd6c2332f
