diff options
| author | Anthony Stange <stange@google.com> | 2019-08-02 13:11:39 -0400 |
|---|---|---|
| committer | Anthony Stange <stange@google.com> | 2019-10-31 09:13:45 -0400 |
| commit | 2ca49ab77bdbd4c2509ea0dfb6710fe7063cfc7d (patch) | |
| tree | 6e37fd3f263907566b78286bcb68a78649952cec /identity/support/src/cppbor_parse.cpp | |
| parent | 6c639cd76568f023119ef705b55cc0beaaf50f11 (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
Merged-In: Ifba4262b68ec0c4ca6921dad40a03e0a52088d28
(cherry picked from commit 4bdd8fc7749db53f477533d01c1234e60afa70a8)
Diffstat (limited to 'identity/support/src/cppbor_parse.cpp')
0 files changed, 0 insertions, 0 deletions