diff options
| author | Anthony Stange <stange@google.com> | 2019-08-02 13:11:39 -0400 |
|---|---|---|
| committer | Brian Duddie <bduddie@google.com> | 2019-08-02 15:08:30 -0700 |
| commit | 4bdd8fc7749db53f477533d01c1234e60afa70a8 (patch) | |
| tree | c387405340bf9793409db5650f17ff83a2b41328 /identity/support/src/cppbor_parse.cpp | |
| parent | df6e2b70aef693e17a7d25034c7723009b31220b (diff) | |
Change expected return type in direct report VTS
If a sensor doesn't support a particular memory type for direct
reporting, then registerChannel will return an invalid channel handle.
When this handle is used in configureDirectReport, it will return
BAD_VALUE and when used in unregisterDirectReport, it will return OK.
Currently, the VTS tests assert it will return INVALID_OPERATION, but
that will only happen if the entire HAL doesn't support direct
reporting instead of a single sensor not supporting a certain memory
type.
Bug: 138758242
Test: Run VTS and verify DirectChannel* tests now pass
Change-Id: Ifba4262b68ec0c4ca6921dad40a03e0a52088d28
Diffstat (limited to 'identity/support/src/cppbor_parse.cpp')
0 files changed, 0 insertions, 0 deletions