Camera: Describe framerate session parameter corner case

A corner case exists during framerate session parameter
updates in constrained HFR mode. The framework will only
monitor for fps upper range modifications.

Bug: 78494729
Test: Camera CTS
Change-Id: I88d59163c060f6e19b3d9f30925b2c5b03077d71

diff --git a/camera/docs/docs.html b/camera/docs/docs.html
index 6d9a398..f64b38a 100644 (file)
--- a/camera/docs/docs.html
+++ b/camera/docs/docs.html
@@ -17576,7 +17576,12 @@ An example usage scenario could look like this:</p>
           </tr>
           <tr class="entry_cont">
             <td class="entry_details" colspan="6">
-              <p>Vendor tags can be listed here.<wbr/> Vendor tag metadata should also
+              <p>If <a href="#controls_android.control.aeTargetFpsRange">android.<wbr/>control.<wbr/>ae<wbr/>Target<wbr/>Fps<wbr/>Range</a> is part of the session parameters and constrained high
+speed mode is enabled,<wbr/> then only modifications of the maximum framerate value will be
+monitored by the framework and can trigger camera re-configuration.<wbr/> For more information
+about framerate ranges during constrained high speed sessions see
+<a href="https://developer.android.com/reference/android/hardware/camera2/CameraDevice.html#createConstrainedHighSpeedCaptureSession">CameraDevice#createConstrainedHighSpeedCaptureSession</a>.<wbr/>
+Vendor tags can be listed here.<wbr/> Vendor tag metadata should also
 use the extensions C api (refer to
 android.<wbr/>hardware.<wbr/>camera.<wbr/>device.<wbr/>V3_<wbr/>4.<wbr/>Stream<wbr/>Configuration.<wbr/>session<wbr/>Params for more details).<wbr/></p>
 <p>Setting/<wbr/>getting vendor tags will be checked against the metadata

diff --git a/camera/docs/metadata_definitions.xml b/camera/docs/metadata_definitions.xml
index a224dd3..55f8481 100644 (file)
--- a/camera/docs/metadata_definitions.xml
+++ b/camera/docs/metadata_definitions.xml
@@ -5497,6 +5497,11 @@ xsi:schemaLocation="http://schemas.android.com/service/camera/metadata/ metadata
 
           </details>
           <hal_details>
+          If android.control.aeTargetFpsRange is part of the session parameters and constrained high
+          speed mode is enabled, then only modifications of the maximum framerate value will be
+          monitored by the framework and can trigger camera re-configuration. For more information
+          about framerate ranges during constrained high speed sessions see
+          {@link android.hardware.camera2.CameraDevice#createConstrainedHighSpeedCaptureSession}.
           Vendor tags can be listed here. Vendor tag metadata should also
           use the extensions C api (refer to
           android.hardware.camera.device.V3_4.StreamConfiguration.sessionParams for more details).