[libcamera-devel] [PATCH v2 6/6] controls: Remove AeEnable and AeLocked
paul.elder at ideasonboard.com
paul.elder at ideasonboard.com
Tue Aug 16 07:32:51 CEST 2022
On Thu, Aug 11, 2022 at 05:02:19PM +0200, Jacopo Mondi via libcamera-devel wrote:
> 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>
Reviewed-by: Paul Elder <paul.elder at ideasonboard.com>
> ---
> src/libcamera/control_ids.yaml | 18 ------------------
> 1 file changed, 18 deletions(-)
>
> diff --git a/src/libcamera/control_ids.yaml b/src/libcamera/control_ids.yaml
> index 694659af4b7d..f7f8b2e525d8 100644
> --- a/src/libcamera/control_ids.yaml
> +++ b/src/libcamera/control_ids.yaml
> @@ -7,24 +7,6 @@
> # Unless otherwise stated, all controls are bi-directional, i.e. they can be
> # set through Request::controls() and returned out through Request::metadata().
> 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.37.1
>
More information about the libcamera-devel
mailing list