diff options
author | Umang Jain <umang.jain@ideasonboard.com> | 2021-12-03 12:45:12 +0530 |
---|---|---|
committer | Umang Jain <umang.jain@ideasonboard.com> | 2021-12-07 21:32:03 +0530 |
commit | 37c41aa6a69985f99f9540dc89d094df61770fdc (patch) | |
tree | d68bb80b9169cffe10c78b1fa84d2dcf9237fb0d /src/qcam/assets/feathericons/arrow-down.svg | |
parent | f31be76ae67f0eae8c417faa53d8e0281368e0bb (diff) |
android: Apply 1% tolerance to minFrameDuration capping
We have some stream resolution which can provide slightly better
frame duration than what we cap (i.e. 1/30 fps). The problem with
this is CTS complains if the camera goes faster during the test
than minFrameDuration reported for that resolution. For instance,
1080p minFrameDuration:
- Nautilus : 33282000ns
- Soraka : 33147000ns
Both are less than capped minFrameDuration 1/30 fps (33333333.33ns).
This patch considers this situation and doesn't cap the
minFrameDuration if the hardware can provide frame durations slightly
better. The tolerance considered is 1% only from the cap.
Signed-off-by: Umang Jain <umang.jain@ideasonboard.com>
Reviewed-by: Jacopo Mondi <jacopo@jmondi.org>
Reviewed-by: Paul Elder <paul.elder@ideasonboard.com>
Diffstat (limited to 'src/qcam/assets/feathericons/arrow-down.svg')
0 files changed, 0 insertions, 0 deletions