aboutsummaryrefslogtreecommitdiffstats
path: root/src/lc-compliance/results.cpp
diff options
context:
space:
mode:
authorLaurent Pinchart <laurent.pinchart@ideasonboard.com>2021-08-30 01:20:10 +0300
committerLaurent Pinchart <laurent.pinchart@ideasonboard.com>2022-08-10 20:33:28 +0300
commitdfc6d711c9f7f0a9868afa5158aa2089163bded3 (patch)
treef0e6e1825fd93a7b52033df184efb50e097e5469 /src/lc-compliance/results.cpp
parent434edb7b4480a34521aa8741dea02615e9dd714d (diff)
libcamera: Allow concurrent use of cameras from same pipeline handlerHEADmaster
libcamera implements a pipeline handler locking mechanism based on advisory locks on media devices, to prevent concurrent access to cameras from the same pipeline handler from different processes (this only works between multiple libcamera instances, as other processes won't use advisory locks on media devices). A side effect of the implementation prevents multiple cameras created by the same pipeline handler from being used concurrently. Fix this by turning the PipelineHandler lock() and unlock() functions into acquire() and release(), with a use count to replace the boolean lock flag. The Camera class is updated accordingly. As a consequence of this change, the IPU3 pipeline handler will fail to operate properly when the cameras it exposes are operated concurrently. The android.hardware.camera2.cts.MultiViewTest#testDualCameraPreview test fails as a result. This should be fixed in the IPU3 pipeline handler to implement mutual exclusion between cameras. Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com> Tested-by: David Plowman <david.plowman@raspberrypi.com>
Diffstat (limited to 'src/lc-compliance/results.cpp')
0 files changed, 0 insertions, 0 deletions

Privacy Policy