Background:
android.hardware.audio.common was frozen in the upstream tm-dev.
Previously, the interface had only V1 (as the in-development version)
and it was in the VNDK. However, after the freeze, it will have V1 and
V2, and only V1 will remain in the VNDK, because we can't have multiple
versions of the same AIDL interface in VNDK (it's just waste of memory).
android.hardware.audio.core is a new AIDL interface that doesn't exist
in TM. It is also a member of VNDK and imports the audio.common
interface. So far, the import has been done without an explicit version
number (i.e. `imports: ["android.hardware.audio.common"]`). As a result,
V1 was imported before the freeze, and V2 (the latest) will be imported
after the freeze.
Problem:
audio.core depending on audio.common-V2 is NOT allowed since the former
is a member of VNDK, but the latter isn't. VNDK should form a closure.
We are actually hitting this:
```
> error: hardware/interfaces/audio/aidl/Android.bp:71:1: module
"android.hardware.audio.core-V1-ndk" variant
"android_vendor.Tiramisu_arm64_armv8-a_static" (created by module
"android.hardware.audio.core-V1-ndk-generator" (created by module
"android.hardware.audio.core_interface")): (native:vendor:vndk) should
not link to "android.hardware.audio.common-V2-ndk" (native:vendor):
VNDK-core must only depend on VNDK-core or VNDK-SP
```
To fix this, make the dependency to audio.common to be explicit about
the version. This change can't be uploaded to tm-dev as audio.core
doesn't exist there, and must be submitted before the AIDL APIs are
frozen there.
Bug: 225941299
Test: m
Merged-In: Iadc96d558d5c7431b0a2b0cbd28b99319a24ee44
Change-Id: Iadc96d558d5c7431b0a2b0cbd28b99319a24ee44
(cherry picked from commit cc489264af)
This adds basic support for enumerating capabilities
of an audio module, creation of patches, and opening of
I/O streams.
Bug: 205884982
Test: atest VtsHalAudioCoreTargetTest
Merged-In: Ib1ef13c95d338b6ef1bde7d87dcd675fc1d35e85
Change-Id: Ib1ef13c95d338b6ef1bde7d87dcd675fc1d35e85
(cherry picked from commit ee27478264)
... for the same reason as cc489264af
Bug: 225941299
Test: m
Merged-In: I269d61c8c441b3db0832f5450f5e5a84a5989a99
Change-Id: I269d61c8c441b3db0832f5450f5e5a84a5989a99
(cherry picked from commit 446519a370)
Previously, the build rules assumed that the target supports both 64 and
32 bit architectures, which isn't true for 32-bit-only targets. That
caused build breakage on such targets. Fixing that by building the
modules only for the first architecture (64 on 64-only or 64/32 target,
and 32 on 32-only target).
Bug: 241916304
Test: build the 32-bit-only target
Merged-In: I5353ab1561622eae12e2dff87eb0f17b47c3773d
Change-Id: I5353ab1561622eae12e2dff87eb0f17b47c3773d
(cherry picked from commit 3ab5c90104)
As libwifi-hal is migrated to soong, the service is migrated to soong as
well.
Bug: 240099735
Test: CtsWifiTestCases
Merged-In: Ie5a4ec6658d5f6aa3d4902c9c3c4b3bef9ff1cde
Change-Id: Ie5a4ec6658d5f6aa3d4902c9c3c4b3bef9ff1cde
(cherry picked from commit c4ac3355a6)
This CL adds comments to clarify the behavior of
IEvsCameraStrea.notify() when the service attempts to deliver an event,
which is originated from AIDL EVS HAL implementation, to the HIDL
recipients.
Bug: 241722031
Test: treehugger
Change-Id: If6648883f982a90ac30a1636258f896272326c3f
VtsHalEvsTargetTest does not verify any behavior depending on
a frame buffer's color format.
Bug: 240685726
Test: atest VtsHalEvsTargetTest
Change-Id: If8b8c595cfc7404a8122728593f778528b45af15
In the reference implementation of the identity function, there are two places where the memory requested in the openssl algorithm is not released. This memory should be freed.
Test: Vts/Cts
Bug: 242927524
Change-Id: I88ffba39cb6ec887f395122e4670bf9f1a2d8e12
Previously, the build rules assumed that the target supports both 64 and
32 bit architectures, which isn't true for 32-bit-only targets. That
caused build breakage on such targets. Fixing that by building the
modules only for the first architecture (64 on 64-only or 64/32 target,
and 32 on 32-only target).
Bug: 241916304
Test: build the 32-bit-only target
Merged-In: I5353ab1561622eae12e2dff87eb0f17b47c3773d
Change-Id: I5353ab1561622eae12e2dff87eb0f17b47c3773d
(cherry picked from commit 3ab5c90104)
As libwifi-hal is migrated to soong, the service is migrated to soong as
well.
Bug: 240099735
Test: CtsWifiTestCases
Merged-In: Ie5a4ec6658d5f6aa3d4902c9c3c4b3bef9ff1cde
Change-Id: Ie5a4ec6658d5f6aa3d4902c9c3c4b3bef9ff1cde
(cherry picked from commit c4ac3355a6)
am skip reason: Merged-In I3ad2e2000fb0db6a62835e621bc81d77308db140 with SHA-1 e08d14104c is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2186773
Change-Id: I70764e1fb29a2639929ae7a1862d40596a8f1198
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I3ad2e2000fb0db6a62835e621bc81d77308db140 with SHA-1 e08d14104c is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/2186773
Change-Id: I2b314de11b3027cec422322902b307207487de93
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
VtsHalEvsV1_1TargetTest does not verify any behavior depending on
a frame buffer's color format.
Bug: 240685726
Test: atest VtsHalEvsV1_1TargetTest
Change-Id: I592a0a8de5fffd98178d624ee5aac4c28245d056
