summaryrefslogtreecommitdiff
path: root/Documentation/guides/pipeline-handler.rst
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/guides/pipeline-handler.rst')
-rw-r--r--Documentation/guides/pipeline-handler.rst13
1 files changed, 9 insertions, 4 deletions
diff --git a/Documentation/guides/pipeline-handler.rst b/Documentation/guides/pipeline-handler.rst
index 26dc9358..ad2a5beb 100644
--- a/Documentation/guides/pipeline-handler.rst
+++ b/Documentation/guides/pipeline-handler.rst
@@ -610,10 +610,15 @@ information can be found in the `ControlInfoMap`_ class documentation.
.. _ControlInfoMap: https://libcamera.org/api-html/classlibcamera_1_1ControlInfoMap.html
Pipeline handlers register controls to expose the tunable device and IPA
-parameters to applications. Our example pipeline handler only exposes trivial
-controls of the video device, by registering a ``ControlId`` instance with
-associated values for each supported V4L2 control but demonstrates the mapping
-of V4L2 Controls to libcamera ControlIDs.
+parameters to applications and register properties to expose the Camera
+immutable characteristics. Controls and properties which have the ``required``
+field specified in the YAML definition are mandatory to be supported by a Camera
+in order for it to comply with the libcamera API specification.
+
+Our example pipeline handler only exposes trivial controls of the video device,
+by registering a ``ControlId`` instance with associated values for each
+supported V4L2 control but demonstrates the mapping of V4L2 Controls to
+libcamera ControlIDs.
Complete the initialization of the ``VividCameraData`` class by adding the
following code to the ``VividCameraData::init()`` function to initialise the