diff options
| author | Jacopo Mondi <jacopo.mondi@ideasonboard.com> | 2023-08-07 10:13:16 +0200 |
|---|---|---|
| committer | Jacopo Mondi <jacopo.mondi@ideasonboard.com> | 2023-08-07 10:13:16 +0200 |
| commit | 2f3565efb5377768e3c2e1ef85eec99668f485de (patch) | |
| tree | 3813d2d3ed6d4a59e912894dccee8e9a179c5c84 /Documentation/guides | |
| parent | 07a1ac5f01caf27aa309e4e743961123d3609291 (diff) | |
libcamera: Define and use MediaDeviceMatch
The xistingdevice search and match criteria implemented by libcamera
only supports 'media device' based cameras, which are supported in the
Linux kernel by the usage of the V4L2/MC API.
Define a MediaDeviceMatch class derived from DeviceMatch and use it
wherever DeviceMatch was used in order to later introduce new derived
classes to support searching and matching devices of a different type.
Signed-off-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Diffstat (limited to 'Documentation/guides')
| -rw-r--r-- | Documentation/guides/pipeline-handler.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/guides/pipeline-handler.rst b/Documentation/guides/pipeline-handler.rst index 10b9c75c..c3b21a88 100644 --- a/Documentation/guides/pipeline-handler.rst +++ b/Documentation/guides/pipeline-handler.rst @@ -90,7 +90,7 @@ functionalities described above. Below is a brief overview of each of those: registered with it, by creating instances of the ``MediaDevice`` class and storing them. -- `DeviceMatch <https://libcamera.org/api-html/classlibcamera_1_1DeviceMatch.html>`_: +- `MediaDeviceMatch <https://libcamera.org/api-html/classlibcamera_1_1MediaDeviceMatch.html>`_: Describes a media device search pattern using entity names, or other properties. @@ -316,10 +316,10 @@ Matching devices ~~~~~~~~~~~~~~~~ Each pipeline handler registered in libcamera gets tested against the current -system configuration, by matching a ``DeviceMatch`` with the system -``DeviceEnumerator``. A successful match makes sure all the requested components -have been registered in the system and allows the pipeline handler to be -initialized. +system configuration, by matching an instance of a class derived from +``DeviceMatch`` with the system ``DeviceEnumerator``. A successful match makes +sure all the requested components have been registered in the system and allows +the pipeline handler to be initialized. The main entry point of a pipeline handler is the `match()`_ class member function. When the ``CameraManager`` is started (using the `start()`_ function), |