diff options
| author | Hirokazu Honda <hiroh@chromium.org> | 2021-04-04 01:22:47 +0900 |
|---|---|---|
| committer | Laurent Pinchart <laurent.pinchart@ideasonboard.com> | 2021-04-04 01:18:49 +0300 |
| commit | 7d7879833812635f3d34a8b41b93202b4faf4f9c (patch) | |
| tree | a7462e8f610d95b4d44339b62eca5a59273977ff /test/v4l2_subdevice/v4l2_subdevice_test.cpp | |
| parent | cbb580d5afbe4bc5d4a0012fa977d89e8edb547d (diff) | |
android: mm: cros: Handle buffer registration failure
cros::CameraBufferManager::Register() fails if a buffer handle
is invalid. We should mark CameraBuffer as invalid on the failure
of Register().
While the cros::CameraBufferManager Unlock() and Deregister() functions
should be able to handle buffers that haven't been locked and
registered, this isn't an API guarantee, and errors will be logged.
Avoid this by skipping unlocking and unregistration of buffers that
haven't been locked or registered.
Signed-off-by: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Diffstat (limited to 'test/v4l2_subdevice/v4l2_subdevice_test.cpp')
0 files changed, 0 insertions, 0 deletions