summaryrefslogtreecommitdiff
path: root/camera/device/3.4/default/CameraDeviceSession.cpp
AgeCommit message (Collapse)Author
2020-03-05Fix bugprone-use-after-move warningsChih-Hung Hsieh
Bug: 150783499 Test: WITH_TIDY=1 make Change-Id: If257532523674ea6256b72ec765904a8de5bf565
2019-06-06Camera: Use original dataspace/format for 3.5 deviceShuzhen Wang
Starting from CameraDeviceSession 3.5, for IMPLEMENTATION_DEFINED pixel format, configureStreams call uses original format and dataspace instead of the overridden value. This makes sure the HAL interface behavior is consistent between first and subsequent processCaptureRequest() calls. Test: Camera CTS and partner testing Bug: 131864007 Change-Id: Id701141d2c11089ef063fd3f32444212855f84ab
2019-04-04Camera: Avoid using an uninitialized physical camera idEmilian Peev
'mStreamMap' entries can be inserted by several versions of HIDL API calls. If the fields are initialized by an older version, then make sure that newer additions are always initialized in the respective API method. Bug: 73885805 Test: adb shell /data/nativetest64/VtsHalCameraProviderV2_4TargetTest/VtsHalCameraProviderV2_4TargetTest --hal_service_instance=android.hardware.camera.provider@2.4::ICameraProvider/legacy/0 Change-Id: Ib5bd8f608da05f628c52d288c518cebbe964182b
2019-02-14Camera: remove stream_configuration_counter from camera3.hYin-Chia Yeh
Handle the race issue in the wrapper HAL instead of letting HAL implementation handing it. Test: Pixel 3 + camera CTS + GCA Bug: 120986771 Change-Id: Iff97fcaa969bea6668679c57642e4322c4ca5c19
2019-02-12Camera: Handle binder call failure due to static metadata sizeShuzhen Wang
For physical camera static metadata, we should reduce its size before passing it across binder if possible. Test: Camera CTS Bug: 124129552 Change-Id: I0d9129642ddcbb4c1a1c7fcf7a88bac734be4f5a
2019-01-28Camera: support libhardware camera device 3.6Yin-Chia Yeh
Add buffer management API support. Test: VTS to be written. Need Pixel device impl to verify. Bug: 120986771 Change-Id: Icdbc621f8cd17aa0868d3ac361867c44793a268c
2018-08-03Legacy camera shim: add option to free buffers earlierYin-Chia Yeh
This option allows HAL to opt in for the behavior that will free cached buffers earlier if the libhardware HAL implementation doesn't cache/reference the cached buffers internally. Test: buffers are freed earlier when the property is set Bug: 111850884 Change-Id: I3a10b288c7160c86dc7d3a30d04b5c4903917731
2018-05-23Camera: use compact copy when necessaryYin-Chia Yeh
When camera HAL sends redundant metadata (reserved space >> actual used space), create a compact copy to save IPC overhead. Test: Camera CTS/camera app smoke test Bug: 79838637 Change-Id: I02657deb377c43c65d111d1fc894eb3c20ad3b8f
2018-05-03Camera: Set partial results in result batcherEmilian Peev
Camera device session 3.4 has a separate result batcher instance. The partial result count needs to get initialized in the same way as ver. 3.2 otherwise the frame batches can get retired prematurely. Bug: 79106874 Test: Camera CTS, run vts --skip-all-system-status-check --skip-preconditions --primary-abi-only --module VtsHalCameraProviderV2_4Target -l INFO Change-Id: I36bfb5bc448154f80f4cb94edcfd119048361099
2018-03-29Camera: Validate physical camera related metadata field from legacy HALShuzhen Wang
Make sure that num_physcam_metadata, physcam_ids, and physcam_metadata returned from process_capture_result is sane. Test: LogicalCameraDeviceTest Bug: 77218595 Change-Id: Ic4d9823569fb86b20ab2ab21edfc32a0e9f5c9c7
2018-03-09Camera: Do not forward capture_result in error conditionShuzhen Wang
If HAL calls process_capture_result with invalid buffers, the HIDL wrapper shouldn't forward it to camera service, since the CaptureResult structure may not be completely initialized. Test: Run GoogleCamera Bug: 74433802 Change-Id: Iaf20b542af5b11ffbedf709e99137b69d77a9ad3
2018-02-28Camera: add external camera fps controlYin-Chia Yeh
V4L2 doesn't seem to allow changing fps at runtime, so we need to wait until pipeline is idle and reconfigure V4L2 streams. Also update the fps filtering logic to make sure supported fps are consistent as long as the major dimension is the same. Ex: for 4:3 webcams, all 1280*N sizes has the same fps set, or for 16:9 webcams, all N*720 sizes has the same fps set. Bug: 72261912 Change-Id: I534f09bebadb2f532a030a841633a8be7d3a87cc
2018-02-14Merge "Camera: Add support for empty physical settings optimization"TreeHugger Robot
2018-02-12camera.device@3.4/metadata@3.3: Revise MOTION_TRACKING capabilityEino-Ville Talvala
Simplify the API for the P release - Remove new templates - Update docs - Also update some metadata docs from prior changes Test: Revised Camera CTS passes Bug: 63629224 Change-Id: I47fb170052cf6062955278ace624a91e8a0078b3
2018-02-09Camera: Add support for empty physical settings optimizationEmilian Peev
Empty individual physical settings should be allowed after one initial successful request. Bug: 72524845 Test: run vts --skip-all-system-status-check --skip-preconditions --primary-abi-only --module VtsHalCameraProviderV2_4Target -l INFO Change-Id: I18d22a56f5f0e6e1d81a6e8c844697c02bc343a1
2018-01-24camera: Add physical camera metadata in CaptureResultShuzhen Wang
- When physical stream of a logical multi-camera is requested, HAL needs to generate metadata for the physical cameras. - In case no physical stream is requested for the logical multi-camera, no capture result metadata is required for physical camera. - Batch physical and logical metadata within one capture_result call. Test: testLogicalCamera CTS test Bug: 64691172 Change-Id: Id040620f3f0c350711d49341ab31ab88ecd94888
2018-01-23camera.device@3.4: Add MOTION_TRACKING template enumsEino-Ville Talvala
- Extend RequestTemplate with two new values - Add legacy wrapper support for the new templates Test: Builds, camera continues to run. CTS coverage of templates tests new templates as expected. Bug: 63629224 Change-Id: I2a44d86a815690798fa4b8327794c64716d134ee
2018-01-20camera: Add support for individual physical camera requestsEmilian Peev
Multi-camera devices should be able to accept and process individual settings for all physical sensors backing the logical camera. 'CaptureRequest' must be extended to hold these additional physical camera settings. Test: Manual using camera application, camera_client_test, run vts --skip-all-system-status-check --skip-preconditions --primary-abi-only --module VtsHalCameraProviderV2_4Target -l INFO Bug: 64691172 Change-Id: Ia38d1e7681a9385be7578c11e40f4e35e9101d75
2018-01-20camera: Add support for logical cameraShuzhen Wang
- Add physical cameraId field in stream structure. - Override processCaptureRequest due to physicalCameraId change. - Update 3.3 metadata with logical camera characteristics. Test: Camera CTS on Taimen, LogicalCamera CTS test on C1 Bug: 64691172 Change-Id: I65bd1ae38381ecb89fae439ae14b813c9bcc3248
2017-12-20Camera: Bump device version to 3.4Emilian Peev
Camera devices supporting version 3.4 will be able to receive session parameters during the stream configuration phase. Bug: 64450664 Test: Camera CTS run commandAndExit vts --skip-all-system-status-check --skip-preconditions --primary-abi-only --module VtsHalCameraProviderV2_4Target -l INFO Change-Id: Ifd83bfe0e512fe75b63602b4aba98f4cc1cdeb53
generated by cgit v1.2.3 (git 2.25.1) at 2025-10-03 18:35:26 +0000