libcamera/Documentation/guides
Naushir Patuck 0455bbbf51 build: controls: Rework how controls and properties are generated
Add support for using separate YAML files for controls and properties
generation. The mapping of vendor/pipeline handler to control file is
done through the controls_map variable in include/libcamera/meson.build.

This simplifies management of vendor control definitions and avoids
possible merge conflicts when changing the control_ids.yaml file for
core and draft controls. With this change, libcamera and draft controls
and properties files are designated the 'libcamera' vendor tag.

In this change, we also rename control_ids.yaml -> control_ids_core.yaml
and property_ids.yaml -> property_ids_core.yaml to designate these as
core libcamera controls.

Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
2023-11-29 09:05:38 +00:00
..
application-developer.rst Documentation: Small typo fix 2023-02-12 20:01:25 +02:00
introduction.rst pipeline: ipa: raspberrypi: Refactor and move the Raspberry Pi code 2023-05-04 20:47:40 +03:00
ipa.rst meson: ipa: Add mapping for pipeline handler to mojom interface file 2023-05-04 18:38:25 +03:00
pipeline-handler.rst build: controls: Rework how controls and properties are generated 2023-11-29 09:05:38 +00:00
tracing.rst guides: tracing: Mention where to find the trace file 2021-12-01 15:42:55 +00:00