From eba862b0e30e73d1e1b05845a8c932bc0ff576ee Mon Sep 17 00:00:00 2001 From: Jacopo Mondi Date: Wed, 24 Feb 2021 13:22:27 +0100 Subject: android: post_processor: Use CameraBuffer API Use the newly introduced CameraBuffer class as the type for the destination buffer in the PostProcessor class hierarchy in place of the libcamera::MappedFrameBuffer one and use its API to retrieve the length and the location of the CameraBuffer plane allocated for JPEG post-processing. Remove all the assumption on the underlying memory storage and only go through the CameraBuffer API when dealing with memory buffers. To do so rework the Encoder interface to use a raw pointer and an explicit size to remove access to the Span maps that serve as memory storage for the current implementation but might not be ideal for other memory backend. Now that the whole PostProcessor hierarchy has been converted to use the CameraBuffer API remove libcamera::MappedBuffer as base class of the CameraBuffer interface and only reply on its interface. Reviewed-by: Laurent Pinchart Signed-off-by: Jacopo Mondi --- src/android/mm/generic_camera_buffer.cpp | 1 + 1 file changed, 1 insertion(+) (limited to 'src/android/mm') diff --git a/src/android/mm/generic_camera_buffer.cpp b/src/android/mm/generic_camera_buffer.cpp index 0fb6b0a9..45a83c35 100644 --- a/src/android/mm/generic_camera_buffer.cpp +++ b/src/android/mm/generic_camera_buffer.cpp @@ -7,6 +7,7 @@ #include "../camera_buffer.h" +#include #include "libcamera/internal/log.h" using namespace libcamera; -- cgit v1.2.1