commit | e48057a2ddb5a5f563d8184357379e9a96aa2de9 | [log] [tgz] |
---|---|---|
author | Hans Chen <junyec@google.com> | Thu Aug 09 10:35:18 2018 -0700 |
committer | Zhuoyao Zhang <zhuoyao@google.com> | Sun Aug 12 21:15:34 2018 +0000 |
tree | 52424d22cd4f7843fa4b71a933387d7c6ba6208f | |
parent | 52b0a932d9ce8ffd00c4160717a94dcf1111501d [diff] |
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
VTS consists of a set of testing frameworks and test cases, designed to help enhance the robustness, reliability, and compliance of:
VTS has mainly two types of test suites:
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