From b24806f9d0d0dcbac7f55439c899c99bdd4c15d9 Mon Sep 17 00:00:00 2001 From: Shuzhen Wang Date: Wed, 27 Feb 2019 08:57:43 -0800 Subject: [PATCH] Camera: ndk: Improve docs for activePhysicalId metadata key Test: Read updated docs Bug: 125346954 Change-Id: I0f0c071a98fb5f23c3db257d3e5cb63a96e8fad8 --- camera/ndk/include/camera/NdkCameraMetadataTags.h | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/camera/ndk/include/camera/NdkCameraMetadataTags.h b/camera/ndk/include/camera/NdkCameraMetadataTags.h index 8c19e1d6cb..b200abf4e8 100644 --- a/camera/ndk/include/camera/NdkCameraMetadataTags.h +++ b/camera/ndk/include/camera/NdkCameraMetadataTags.h @@ -5688,13 +5688,17 @@ typedef enum acamera_metadata_tag { * *

The ID of the active physical camera that's backing the logical camera. All camera * streams and metadata that are not physical camera specific will be originating from this - * physical camera. This must be one of valid physical IDs advertised in the physicalIds - * static tag.

+ * physical camera.

*

For a logical camera made up of physical cameras where each camera's lenses have * different characteristics, the camera device may choose to switch between the physical * cameras when application changes FOCAL_LENGTH or SCALER_CROP_REGION. * At the time of lens switch, this result metadata reflects the new active physical camera * ID.

+ *

This key will be available if the camera device advertises this key via {@link ACAMERA_REQUEST_AVAILABLE_RESULT_KEYS }. + * When available, this must be one of valid physical IDs backing this logical multi-camera. + * If this key is not available for a logical multi-camera, the camera device implementation + * may still switch between different active physical cameras based on use case, but the + * current active physical camera information won't be available to the application.

*/ ACAMERA_LOGICAL_MULTI_CAMERA_ACTIVE_PHYSICAL_ID = // byte ACAMERA_LOGICAL_MULTI_CAMERA_START + 2,