These are required to build. Separate CL to preserve blame history.
From running 'update-includes.sh' script here.
Bug: 37280010
Test: boot/build (sanity)
Change-Id: Id9c2dc37f674b27b947a9f823bd38a550d64d31b
This splits headers into three locations:
include - for backwards compatibility, the global include
include_all - for things system/vendor both use
include_vendor - for things that only vendors use
The goal is to gradually have system things stop referencing
(at least most) of these headers.
Bug: 37280010
Test: build (CL on top adds back in symlinks)
Change-Id: Ibf194276b7faa857e1e7605d7719f4e7d873ecba
Extend "CAMERA3_MSG_ERROR_RESULT" comments and describe
how Hal must notify about physical device result failures
and logical device result failures.
Bug: 128835627
Test: Successful build
Change-Id: I935fba5a5676a0fe9440f43b281fc9eeb50578ea
The race condition is now handled by default HAL wrapper so
we don't need to send this information to HAL implementation.
Test: Pixel 3 + Camera CTS + GCA
Bug: 120986771
Change-Id: I48e611ba45d45ebf34359e828bcb23cb6eec4af2
Enable Hal to trigger or skip stream reconfiguration
based on session parameter updates.
Bug: 122609098
Test: Manual using application,
VtsHalCameraProviderV2_4TargetTest
--hal_service_instance=android.hardware.camera.provider@2.4::ICameraProvider/legacy/0
--gtest_filter=CameraHidlTest.configureStreamsWithSessionParameters
Change-Id: Ie931e7cb7f46257276cc1796fccd301c85a90d85
- Add new BlobId to specify JPEG APP segments.
- Add new gralloc usage flag for HEIC encoder.
Test: testHeic CTS test
Bug: 79465976
Change-Id: Ie70654504eecb280e3a51b60c104124035c5fbe5
- Add an array of physical camera ids and metadata when physical
cameras are requested within a logical multi-camera.
- Physical camera ids and metadata are only necessary for the final
capture_results, not the partial result.
- Physical camera ids and metadata must not be populated if no physical
camera is requested.
Test: Compile
Bug: 64691172
Change-Id: I78b20fe3d0c6462abf95b8fe7e3b4c66b3acefdf
The legacy camera 3.5 API should allow clients to set individual
settings for specific physical cameras that are part of
a logical multi-camera. 'camera3_capture_request_t' must
include additional arrays containing the required settings
and corresponding camera ids.
Test: Manual using camera application,
camera_client_test
Bug: 64691172
Change-Id: I634f1d5b87a6d97c5a35b8ea633c7a6c22793eaf
- Add ability to specify the camera id to which a particular camera3_stream belongs.
- Update documentation about the camera characteristics of logical camera.
Test: Camera2.apk and GoogleCamera.apk
Bug: 64691172
Change-Id: Ie2e235e8bc8124596785db8dad25549bec4232aa
This version update adds support for session keys and
session parameters.
Bug: 64450664
Test: Camera CTS
Change-Id: Id14dbde5083c974b86b942dfd6e904dbe85e0ee5
Specify the HAL behavior when stream usage flag is combination for
multiple consumers.
Test: Compile
Bug: 33777818
Change-Id: If11de5d249b1a8366dad7ec14e5e35f9cfc06ce4
Now cameraservice only sends one shutter notify and capture result to
the application per batch. Update the HAL interface doc to reflect this.
Test: Compiles
Bug: 35775704
Change-Id: I290ef93f842f4a02e5bdaeb0e50298f79fcef602
- Few additional mandatory static metadata fields
- Different dataspace encoding than HAL v3.3
- A few additional general-use metadata fields
Bug: 27344373
Change-Id: I218cc9fa70d1227cd96155e126edcf9be699ea2d
Document how HAL should operate when process_capture_request is
called while a flush() call is active.
Bug: 21506384
Change-Id: Ic1842add68123432e49914e83d8f7d5c13d6650d
Clarify that the SHUTTER event should be sent when HAL
start processing a reprocess request but the timestamp
should be the input image's start of exposure.
Bug: 21112186
Change-Id: I5bd32b749adc5e82e9a311ec4b123fd807a30d36
This allows application or framework request HAL to perform a
rotation of 0, 90, 180 or 270 degrees counterclockwise. Currently
there is no plan to support arbitrary rotation angles.
HAL should return -EINVAL if the requested rotation cannot be
supported.
Change-Id: I8bde2bcfd797c408db4d5b391b170a4e856ec2d0
The dataspace field communicates extra context about the requested
stream configuration. For most graphics formats, the dataspace
indicates the desired colorspace out of the output buffers. For some
formats, the dataspace may indicate that depth output is requested
instead.
Change-Id: I6746d9097b4dc36af0a63ca88df75f32a77db90b
INPUT stream is not used by framework-implemented ZSL (HAL3.2), the sample
use case description is incorrect.
Bug: 19197776
Change-Id: I247ad8755b2197c2a62cc109c151749b42a4bd49
For HAL3.2 or above, the HAL must return the input buffer in capture result
rather than capture request.
Change-Id: I0108cda1cdf51556d7273b2c3cfbaf0e6ecd1d76
- Deprecates vendor tag specification in camera3 device.
- Moves vendor tag ops declaration to camera metadata library and
cleans up definitions.
- Updates the example HAL.
Change-Id: Ifb16bb0d4bbc896bc32d33dd150e7e174af57dad
Needed to support the real case of continuous focus giving up on a
scene for a while (say, a blank wall), during which we shouldn't claim
the lens is in motion.
Also add new states for INACTIVE to clarify it as the starting state
after mode transitions or enabling AF/AE/AWB.
Bug: 10860639
Bug: 10446772
Change-Id: Ie4c1ac73e5a9eb6d1894d83dbded49a2767a8ffd
