.. SPDX-License-Identifier: CC-BY-SA-4.0 Environment variables ===================== The libcamera behaviour can be tuned through environment variables. This document lists all the available variables and describes their usage. List of variables ----------------- LIBCAMERA_LOG_FILE The custom destination for log output. Example value: ``/home/{user}/camera_log.log`` LIBCAMERA_LOG_LEVELS Configure the verbosity of log messages for different categories (`more `__). Example value: ``*:DEBUG`` LIBCAMERA_IPA_CONFIG_PATH Define custom search locations for IPA configurations (`more `__). Example value: ``${HOME}/.libcamera/share/ipa:/opt/libcamera/vendor/share/ipa`` LIBCAMERA_IPA_FORCE_ISOLATION When set to a non-empty string, force process isolation of all IPA modules. Example value: ``1`` LIBCAMERA_IPA_MODULE_PATH Define custom search locations for IPA modules (`more `__). Example value: ``${HOME}/.libcamera/lib:/opt/libcamera/vendor/lib`` Further details --------------- Notes about debugging ~~~~~~~~~~~~~~~~~~~~~ The environment variables ``LIBCAMERA_LOG_FILE`` and ``LIBCAMERA_LOG_LEVELS`` are used to modify the destination and verbosity of messages provided by libcamera. The ``LIBCAMERA_LOG_LEVELS`` variable accepts a comma-separated list of 'category:level' pairs. The `level `__ part is mandatory and can either be specified by name or by numerical index associated with each level. The optional `category `__ is a string matching the categories defined by each file in the source base using the logging infrastructure. It can include a wildcard ('*') character at the end to match multiple categories. For more information refer to the `API documentation `__. Examples: Enable full debug output to a separate file, for every `category `__ within a local environment: .. code:: bash :~$ LIBCAMERA_LOG_FILE='/tmp/example_log.log' \ LIBCAMERA_LOG_LEVELS=0 \ cam --list Enable full debug output for the categories ``Camera`` and ``V4L2`` within a global environment: .. code:: bash :~$ export LIBCAMERA_LOG_LEVELS='Camera:DEBUG,V4L2:DEBUG' :~$ cam --list Log levels ~~~~~~~~~~~ This is the list of available log levels, notice that all levels below the chosen one are printed, while those above are discarded. - DEBUG (0) - INFO (1) - WARN (2) - ERROR (3) - FATAL (4) Example: If you choose WARN (2), you will be able to see WARN (2), ERROR (3) and FATAL (4) but not DEBUG (0) and INFO (1). Log categories ~~~~~~~~~~~~~~~ Every category represents a specific area of the libcamera codebase, the names can be located within the source code, for example: `src/libcamera/camera_manager.cpp `__ .. code:: cpp LOG_DEFINE_CATEGORY(Camera) There are two available macros used to assign a category name to a part of the libcamera codebase: LOG_DEFINE_CATEGORY This macro is required, in order to use the ``LOGC`` macro for a particular category. It can only be used once for each category. If you want to create log messages within multiple compilation units for the same category utilize the ``LOG_DECLARE_CATEGORY`` macro, in every file except the definition file. LOG_DECLARE_CATEGORY Used for sharing an already defined category between multiple separate compilation units. Both macros have to be used within the libcamera namespace of the C++ source code. IPA configuration ~~~~~~~~~~~~~~~~~ IPA modules use configuration files to store parameters. The format and contents of the configuration files is specific to the IPA module. They usually contain tuning parameters for the algorithms, in JSON format. The ``LIBCAMERA_IPA_CONFIG_PATH`` variable can be used to specify custom storage locations to search for those configuration files. `Examples `__ IPA module ~~~~~~~~~~~ In order to locate the correct IPA module for your hardware, libcamera gathers existing IPA modules from multiple locations. The default locations for this operation are the installed system path (for example on Debian: ``/usr/local/x86_64-pc-linux-gnu/libcamera``) and the build directory. With the ``LIBCAMERA_IPA_MODULE_PATH``, you can specify a non-default location to search for IPA modules. ref='/libcamera/jmondi/libcamera.git/tree/src/ipa?h=imx8mp/extensible-format&id=ae7809307e798ae32f4c978882aca94249ce7fd7'>ipa/libipa/fc_queue.cpp
blob: e812faa505a54ca253fb916c5e547be613278daa (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
/* SPDX-License-Identifier: LGPL-2.1-or-later */
/*
 * Copyright (C) 2022, Google Inc.
 *
 * fc_queue.cpp - IPA Frame context queue
 */

#include "fc_queue.h"

#include <libcamera/base/log.h>

namespace libcamera {

LOG_DEFINE_CATEGORY(FCQueue)

namespace ipa {

/**
 * \file fc_queue.h
 * \brief Queue of per-frame contexts
 */

/**
 * \struct FrameContext
 * \brief Context for a frame
 *
 * The frame context stores data specific to a single frame processed by the
 * IPA module. Each frame processed by the IPA module has a context associated
 * with it, accessible through the Frame Context Queue.
 *
 * Fields in the frame context should reflect values and controls associated
 * with the specific frame as requested by the application, and as configured by
 * the hardware. Fields can be read by algorithms to determine if they should
 * update any specific action for this frame, and finally to update the metadata
 * control lists when the frame is fully completed.
 *
 * \var FrameContext::frame
 * \brief The frame number
 */

/**
 * \class FCQueue
 * \brief A support class for managing FrameContext instances in IPA modules
 * \tparam FrameContext The IPA module-specific FrameContext derived class type
 *
 * Along with the Module and Algorithm classes, the frame context queue is a
 * core component of the libipa infrastructure. It stores per-frame contexts
 * used by the Algorithm operations. By centralizing the lifetime management of
 * the contexts and implementing safeguards against underflows and overflows, it
 * simplifies IPA modules and improves their reliability.
 *
 * The queue references frame contexts by a monotonically increasing sequence
 * number. The FCQueue design assumes that this number matches both the sequence
 * number of the corresponding frame, as generated by the camera sensor, and the
 * sequence number of the request. This allows IPA modules to obtain the frame
 * context from any location where a request or a frame is available.
 *
 * A frame context normally begins its lifetime when the corresponding request