X-Git-Url: http://git.osdn.net/view?a=blobdiff_plain;f=camera%2Fdocs%2Fdocs.html;h=f4c60ecf8e38a1dad5bc57e5f5f9cc68900ac78f;hb=6916b4fbf7c2941ad28204eef9557421a578e6ec;hp=531089673bd75210163051b0353296ae71b73a67;hpb=d24b970411ba3103ca018f478b876fd791e8a909;p=android-x86%2Fsystem-media.git diff --git a/camera/docs/docs.html b/camera/docs/docs.html index 53108967..f4c60ecf 100644 --- a/camera/docs/docs.html +++ b/camera/docs/docs.html @@ -17400,11 +17400,7 @@ of keys that can be overriden using Builder#getPhysicalCameraKey. Capture requests that contain individual physical device requests must be built via -Set). -Such extended capture requests can be passed only to -CameraCaptureSession#capture or CameraCaptureSession#captureBurst and -not to CameraCaptureSession#setRepeatingRequest or -CameraCaptureSession#setRepeatingBurst.

+Set).

@@ -17421,6 +17417,9 @@ details).

vendor extensions API and not against this field.

The HAL must not consume any request tags in the session parameters that are not listed either here or in the vendor tag list.

+

There should be no overlap between this set of keys and the available session keys +CameraCharacteristics#getAvailableSessionKeys along +with any other controls that can have impact on the dual-camera sync.

The public camera2 API will always make the vendor tags visible via CameraCharacteristics#getAvailablePhysicalCameraRequestKeys.