Change proto message to accomodate FMQ driver refactor

Test: make vts -j
Changes:
* Add a new operation to get queue descriptor address for internal use.
* A new field that specifies queue descriptor address, which is used to create the queue. Internal use only.
* Rename FMQ_PROTO_* into FMQ_* because we won't define another set of
operations in FMQ driver.
* Change host-side implementation to accomodate the change in proto.

Merged-In: Icc667865bd4a17614e2f9ee2667e34ab3b19b256
Change-Id: Icc667865bd4a17614e2f9ee2667e34ab3b19b256
3 files changed
tree: 52424d22cd4f7843fa4b71a933387d7c6ba6208f
  1. agents/
  2. compilation_tools/
  3. doc/
  4. drivers/
  5. hals/
  6. harnesses/
  7. proto/
  8. runners/
  9. script/
  10. specification/
  11. testcases/
  12. tools/
  13. utils/
  14. .clang-format
  15. .gitignore
  16. __init__.py
  17. Android.bp
  18. OWNERS
  19. PREUPLOAD.cfg
  20. README.md
  21. setup.py
README.md

Android Vendor Test Suite (VTS)

VTS consists of a set of testing frameworks and test cases, designed to help enhance the robustness, reliability, and compliance of:

  • the Android system (e.g., Core HALs and libraries) and
  • low-level system software (e.g., kernel, module, and firmware).

VTS has mainly two types of test suites:

  • automated (e.g., record-and-replay and fuzzing) and
  • structural (e.g., gTest and host-driven python) testing.

While the VTS framework and test cases are designed for userdebug or eng build devices, some test cases can be run on user build devices using its app namely, VTS Agent App.

Table of Contents

  1. VTS User Manual
  2. Where to find VTS test cases
  3. VTS Test Developer Manual (Codelab)