diff options
author | Umang Jain <umang.jain@ideasonboard.com> | 2021-09-29 19:00:30 +0530 |
---|---|---|
committer | Umang Jain <umang.jain@ideasonboard.com> | 2021-09-30 18:28:36 +0530 |
commit | d79b41200199e03834578f5120bb8375bad37aec (patch) | |
tree | 95ca99b71cfcd9bb862624c437e1e18135820a2d /test/v4l2_subdevice/list_formats.cpp | |
parent | 05c87a36cbad36db55e6a1d59ace7bbd5f6e3691 (diff) |
android: camera_device: Send capture results by inspecting the queue
There is a possibility that an out-of-order completion of capture
request happens by calling process_capture_result() directly on error
paths. The framework expects that errors should be notified as soon as
possible, but the request completion order should remain intact.
An existing instance of this is abortRequest(), which sends the capture
results on flushing state, without considering order-of-completion.
Since we have a queue of Camera3RequestDescriptor tracking each
capture request placed by framework to libcamera HAL, we should be only
sending back capture results from a single location, by inspecting
the queue. As per the patch, this now happens in
CameraDevice::sendCaptureResults().
Each descriptor is now equipped with its own status to denote whether
the capture request is complete and ready to be send back to the
framework or needs to be waited upon. This ensures that the order of
completion is respected for the requests.
Since we are fixing out-of-order request completion in abortRequest(),
change the function to read from the Camera3RequestDescriptor directly,
instead of camera3_capture_request_t. The descriptor should have all the
information necessary to set the request buffers' state to error.
Signed-off-by: Umang Jain <umang.jain@ideasonboard.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Jacopo Mondi <jacopo@jmondi.org>
Diffstat (limited to 'test/v4l2_subdevice/list_formats.cpp')
0 files changed, 0 insertions, 0 deletions