Revert "Change payload type to int32_t for fmq device tests"
Revert submission 1431616-thirtytwo
Reason for revert: This topic broke the aosp_x86-userdebug target. Details at http://b/169077648
Reverted Changes:
If736389eb:Add template parameters to MQDescriptor
Ice9c28c3d:Change HIDL fmq tests to use int32_t for payload
Ia18d8459b:Add template arguments to MQDescriptor for AIDL
I95586cc83:Change payload type to int32_t for fmq device test...
Change-Id: Ib7c409b164c76517d642a415cdfc2406e4f2f351
First parameter is used to determine the type of the payload, and the
second parameter is used to determine the type of queue.
Added two types to be use in that second parameter.
SynchronizedReadWrite and UnsynchronizedWrite.
Test: atest fmq_unit_tests fmq_test
Bug: 142326204
Change-Id: If736389ebecd02b87879850714606523e5145579
Adding these two types to android.hardware.common for future use with
Fast Message Queue in libfmq.
Also adding to the mq_test_service to test them.
Test: system/tools/hidl/tests/run_all_device_tests.sh
Bug: 142326204
Change-Id: I424c4849c822436f58e40f206b09ffdf9baf260b
Generated files with:
m android.hardware.common-update-api
m android.hardware.graphics.common-update-api
Test: Builds
We don't want this commit merged into branches that have added
these types already, as they may have changed.
Merged-In: Ie1d92a50dddf7e3e1bd473e2a957279c6dadb865
Change-Id: I2d83dfdb1d0ba75c76774ded26c4ce93b1807097
AIDL interfaces which are vintf-stable have to be frozen in release.
But these interfaces have been never frozen, so freeze them.
- android.hardware.common
- android.hardware.automotive.occupant_awareness
- android.hardware.rebootescrow
- android.hardware.graphics.common
Bug: 153510296
Bug: 153510400
Bug: 153510960
Bug: 153511702
Test: m
Change-Id: I56e53209eaf00518ec83f2a322e89d6d944eb0ac
All aidl_interface modules should by default considered as stable, in
case it is used across system and vendor partitions, or across modules.
Like other API surfaces, we need to have a dump for the current
(yet-to-be-released) version and update it when there is an API change.
This is done via .
Then the owner of the interface can freeze the current version as a
numbered version via .
This change shal be rejected only when the owner is certain that the
interface is not used across the updatable boundaries.
Bug: 152655547
Test: m
Change-Id: Icc9c32aaf7f8555e6a3792bb5e5a2b48a446c545
