summaryrefslogtreecommitdiff
path: root/src/libcamera/camera.cpp
diff options
context:
space:
mode:
authorLaurent Pinchart <laurent.pinchart@ideasonboard.com>2020-03-14 16:14:27 +0200
committerLaurent Pinchart <laurent.pinchart@ideasonboard.com>2020-03-18 19:15:18 +0200
commit33fedea818e2b6a9ed68ac86acf194b1a2da8828 (patch)
treeb350f4bc1710775cfe82af3bd7b1f36ce9ee5d2a /src/libcamera/camera.cpp
parent9da27d5d844fa1378a4897a637c45ade275cc7e5 (diff)
libcamera: pipeline_handler: Fold buffer management with start/stop
There's no need anymore to have the Camera object control how and when pipeline handlers allocate and free the buffers for the application-facing video devices. Fold those operations, currently performed by importFrameBuffers() and freeFrameBuffers(), into the start() and stop() functions. This simplifies the pipeline handler API, its implementation, and the implementation of the Camera class. Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Reviewed-by: Niklas Söderlund <niklas.soderlund@ragnatech.se>
Diffstat (limited to 'src/libcamera/camera.cpp')
-rw-r--r--src/libcamera/camera.cpp11
1 files changed, 0 insertions, 11 deletions
diff --git a/src/libcamera/camera.cpp b/src/libcamera/camera.cpp
index 3192dfb4..5593c1b3 100644
--- a/src/libcamera/camera.cpp
+++ b/src/libcamera/camera.cpp
@@ -915,13 +915,6 @@ int Camera::start()
LOG(Camera, Debug) << "Starting capture";
- for (Stream *stream : p_->activeStreams_) {
- ret = p_->pipe_->invokeMethod(&PipelineHandler::importFrameBuffers,
- ConnectionTypeDirect, this, stream);
- if (ret < 0)
- return ret;
- }
-
ret = p_->pipe_->invokeMethod(&PipelineHandler::start,
ConnectionTypeBlocking, this);
if (ret)
@@ -959,10 +952,6 @@ int Camera::stop()
p_->pipe_->invokeMethod(&PipelineHandler::stop, ConnectionTypeBlocking,
this);
- for (Stream *stream : p_->activeStreams_)
- p_->pipe_->invokeMethod(&PipelineHandler::freeFrameBuffers,
- ConnectionTypeBlocking, this, stream);
-
return 0;
}