summaryrefslogtreecommitdiff
path: root/src/ipa/raspberrypi/controller/sharpen_algorithm.h
diff options
context:
space:
mode:
authorLaurent Pinchart <laurent.pinchart@ideasonboard.com>2022-10-20 00:44:55 +0300
committerLaurent Pinchart <laurent.pinchart@ideasonboard.com>2022-10-20 13:36:25 +0300
commit84ad104499d9efc0253dae1a60ee070ed375ad95 (patch)
treed10fd53eb79cebb28fa3f72b18b46dddb6382b83 /src/ipa/raspberrypi/controller/sharpen_algorithm.h
parentdaf3f4b59f4ea0ecb42c6a39fe909f071d3a2842 (diff)
Move test applications to src/apps/
The cam and qcam test application share code, currently through a crude hack that references the cam source files directly from the qcam meson.build file. To prepare for the introduction of hosting that code in a static library, move all applications to src/apps/. Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Reviewed-by: Paul Elder <paul.elder@ideasonboard.com> Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
Diffstat (limited to 'src/ipa/raspberrypi/controller/sharpen_algorithm.h')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.1 (git 2.18.0) at 2025-06-08 02:03:48 +0000
79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 
/* SPDX-License-Identifier: LGPL-2.1-or-later */
/*
 * Copyright (C) 2021, Google Inc.
 *
 * fence.cpp - Synchronization fence
 */

#include "libcamera/fence.h"

namespace libcamera {

/**
 *
 * \file libcamera/fence.h
 * \brief Definition of the Fence class
 */

/**
 * \class Fence
 * \brief Synchronization primitive to manage resources
 *
 * The Fence class models a synchronization primitive that can be used by
 * applications to explicitly synchronize resource usage, and can be shared by
 * multiple processes.
 *
 * Fences are most commonly used in association with frame buffers. A
 * FrameBuffer can be associated with a Fence so that the library can wait for
 * the Fence to be signalled before allowing the camera device to actually
 * access the memory area described by the FrameBuffer.
 *
 * \sa Request::addBuffer()
 *
 * By using a fence, applications can then synchronize between frame buffer
 * consumers and producers, as for example a display device and a camera, to
 * guarantee that a new data transfers only happen once the existing frames have
 * been displayed.
 *
 * A Fence can be realized by different event notification primitives, the most
 * common of which is represented by waiting for read events to happen on a
 * <a href="https://www.kernel.org/doc/html/latest/driver-api/sync_file.html">kernel sync file.</a>
 * This is currently the only mechanism supported by libcamera, but others can
 * be implemented by extending or subclassing this class and implementing
 * opportune handling in the core library.
 *
 * \internal
 *
 * The Fence class is a thin abstraction around a UniqueFD which simply allows