[PATCH v4 8/8] controls: Remove AeEnable and AeLocked

Paul Elder paul.elder at ideasonboard.com
Thu Dec 5 12:22:41 CET 2024


From: Jacopo Mondi <jacopo at jmondi.org>

Now that the codebase has been ported to use the new AEGC controls
remove the definition of AeEnable and AeLocked.

Signed-off-by: Jacopo Mondi <jacopo at jmondi.org>
Signed-off-by: Paul Elder <paul.elder at ideasonboard.com>
Reviewed-by: Paul Elder <paul.elder at ideasonboard.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart at ideasonboard.com>

---
No change in v4

No change in v3
---
 src/libcamera/control_ids_core.yaml | 18 ------------------
 1 file changed, 18 deletions(-)

diff --git a/src/libcamera/control_ids_core.yaml b/src/libcamera/control_ids_core.yaml
index 65d72aa35789..fb76499f9dcd 100644
--- a/src/libcamera/control_ids_core.yaml
+++ b/src/libcamera/control_ids_core.yaml
@@ -8,24 +8,6 @@
 # set through Request::controls() and returned out through Request::metadata().
 vendor: libcamera
 controls:
-  - AeEnable:
-      type: bool
-      description: |
-        Enable or disable the AE.
-
-        \sa ExposureTime AnalogueGain
-
-  - AeLocked:
-      type: bool
-      description: |
-        Report the lock status of a running AE algorithm.
-
-        If the AE algorithm is locked the value shall be set to true, if it's
-        converging it shall be set to false. If the AE algorithm is not
-        running the control shall not be present in the metadata control list.
-
-        \sa AeEnable
-
   - AeState:
       type: int32_t
       description: |
-- 
2.39.2



More information about the libcamera-devel mailing list