Laurent Pinchart c20d3f5575 libcamera: framebuffer: Move remaining private data to Private class ... Private members of the FrameBuffer class are split between FrameBuffer and FrameBuffer::Private. There was no real justification for this split, and keeping some members private in the FrameBuffer class causes multiple issues: - Future modifications of the FrameBuffer class without breaking the ABI may be more difficult. - Mutable access to members that should not be modified by applications require a friend statement, or going through the Private class. Move all remaining private members to the Private class to address the first issue, and add a Private::metadata() function to address the second problem. Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Reviewed-by: Jacopo Mondi <jacopo@jmondi.org> Reviewed-by: Umang Jain <umang.jain@ideasonboard.com> Tested-by: Naushir Patuck <naush@raspberrypi.com>		2022-10-10 17:49:49 +03:00
..
cros_camera_buffer.cpp	android: mm: Null check for CameraBufferManager	2021-11-08 16:50:27 +05:30
cros_frame_buffer_allocator.cpp	libcamera: framebuffer: Move remaining private data to Private class	2022-10-10 17:49:49 +03:00
generic_camera_buffer.cpp	libcamera: Replace toString with operator<<() for format classes	2022-05-04 14:11:33 +03:00
generic_frame_buffer_allocator.cpp	libcamera: framebuffer: Move remaining private data to Private class	2022-10-10 17:49:49 +03:00
meson.build	android: Introduce PlatformFrameBufferAllocator	2021-12-06 17:41:45 +01:00