With this change:
1. We avoid constructing a strong pointer on every call to
getSystemSuspendServiceOnce().
2. In case the function static pointer is corrupted, the error
propagates to the API call where we're able to handle the errors instead
of the compiler-generated code in the return statement of
getSystemSuspendServiceOnce().
Bug: 117575503
Test: device builds/boots
Change-Id: I85b5616efca25063c876b242529e2bf561f5b834
Changed:
- simplified getting system suspend service
- added isOk() check when releasing a wake lock
Bug: 117575503
Test: presubmit
Change-Id: I78f1f50a7670e7df88e59999c35f99a6df06e8ef
This change routes libpower and libhardware_legacy to SystemSuspend service for
wake locks instead of /sys/power/wake_[un]lock.
Bug: 78888165
Bug: 115946999
Test: /sys/kernel/debug/suspend_stats shows that device suspends if left alone
Change-Id: Id4d392e13d06be6d86e3112dedeb6a57bb24c06f
This is used to implement readApfPacketFilterData() for legacy wifi
drivers.
Bug: 73804303
Test: builds!
Change-Id: I562911cc064efec747629628df4eab8128449b51
(cherry picked from commit f70b864ede)
libhardware_legacy is the legacy deprecated version
of the legacy and deprecated library libhardware.
In it are defined vendor/system interfaces. One common
pattern is for the following call flow to happen:
<vendor code>
-> legacy interface
-> HIDL
-> legacy interface
-> <framework client code>
Because of this, it's possible to circumvent the stable ABI
provided in HIDL by accidentally passing through data which
is not represented in the vendor interface. This causes
coupling of system/vendor components by way of an undeclared
ABI.
This initial OWNERS file was created with the following groups:
<HIDL specific players>
<common committers> intersect <familiarity with this problem>
Bug: 70526789
Bug: 37280010
Test: N/A
Merged-In: Icebeb958b41cb505d76341f3d53a3e175a3c92bd
Change-Id: Icebeb958b41cb505d76341f3d53a3e175a3c92bd
libhardware_legacy is the legacy deprecated version
of the legacy and deprecated library libhardware.
In it are defined vendor/system interfaces. One common
pattern is for the following call flow to happen:
<vendor code>
-> legacy interface
-> HIDL
-> legacy interface
-> <framework client code>
Because of this, it's possible to circumvent the stable ABI
provided in HIDL by accidentally passing through data which
is not represented in the vendor interface. This causes
coupling of system/vendor components by way of an undeclared
ABI.
This initial OWNERS file was created with the following groups:
<HIDL specific players>
<common committers> intersect <familiarity with this problem>
Bug: 70526789
Bug: 37280010
Test: N/A
Change-Id: Icebeb958b41cb505d76341f3d53a3e175a3c92bd
