Test: Confirm logging of device state notifications occurs
Test: Camera continues to function when switched to 2.5
Change-Id: Iac431770be7659c0f419ba8b002a679f38ecaae2
Add necessary API to support stream combination query.
This will be used in case Hal supports the new 2.5 module
API.
Bug: 111593096
Test: Camera VTS
Change-Id: I916dcbd585e07be16f2f07da0076fb68039d6a00
The new camera_module version adds function to query physical camera
static metadata.
Test: Camera CTS on Pixel devices
Bug: 79523700
Change-Id: I276f23808595b4c6389cb04b19c8c3658b2db967
This version update adds support for session keys and
session parameters.
Bug: 64450664
Test: Camera CTS
Change-Id: Id14dbde5083c974b86b942dfd6e904dbe85e0ee5
- Indicate that HALv3.0 and v3.1 are no longer supported
- Update tests that reuse camera service plumbing to match
service code changes
Test: Builds
Bug: 32991422
Change-Id: I13b800aea6f65270a2a621bd8a61705160fb2dc8
Device HAL v2.x is obsolete, and no devices using it are still
supported. Mark it unsupported, and clean up native tests.
Bug: 25866588
Change-Id: I8e0f1448b8ae0eaaf3714f2351746af46c7657a7
Clarify that HAL shouldn't send AVAILABLE_OFF in addition to
NOT_AVAILABLE when open() is called.
Update the comments to use the right torch status enums.
Bug: 21475390
Change-Id: If9adf4bd169048fc9760ef504d3a36414cfbb196
For use by Camera HAL libraries to perform one-time initialization
steps after the library is loaded.
Bug: 20016050
Change-Id: Ia01ae0eafcadece9124ac2cfcc3b1c3939352843
Update the torch status callback API so that HAL must invoke
the torch status callback whenever the torch status changes
including changes by set_torch_mode().
The problem of the previous approach was camera service needed
to invoke the callback after calling set_torch_mode() and two
sources of the torch status changes (HAL and camera service)
caused a race condition.
Add STATUS_ON and remove STATUS_AVAILABLE which isn't useful
because STATUS_OFF means torch is off and available. STATUS_ON
means torch is on and available.
Bug: 2682206
Change-Id: Ide5d289c5f485404a3ba46e6cb359fa8a52da0bb
To match the public API, seperate camera device in use and other
resources in use errors.
Bug: 2682206
Change-Id: Ie0451931f0c84fc65f3f6294a9f44bec10627afe
Add TORCH_MODE_STATUS_OFF for the case when HAL has to turn off the
torch mode that was turned on by a previous set_torch_mode() call
in order to turn on the torch mode for the current set_torch_mode()
call.
Bug: 2682206
Change-Id: Ia2f717ffaca8c4346ec5fcdf73895160f700f067
- Add necessary metadata to the camera_info structure to allow
the camera service to determine which devices can be safely
opened and used simultaneously without attempting to open
camera devices.
Change-Id: I4250b4c7e1296ebf4cab07355d6d3be01f17ba1e
Inheritance of HAL object is performed by composing a child structure of a
single parent structure located at offset 0 followed by new data members
and function pointers in the child structure.
For example,
struct child {
struct parent common;
int a_data_member;
void (*a_method)(struct child *c, int v);
};
HAL code assumes this layout when accessing child structures given a pointer
to a parent structure such that users write code like the following...
void child_method(struct *parent, int v) {
struct child * c = (struct child*)parent;
// do stuff with c
}
Code above will break if a member is added before "common" in "struct child".
This change adds comments that describe the restriction on the location of
parent HAL objects within a derived HAL object. HAL objects that already
have comments that describe the required location of parent objects are not
modified.
Change-Id: Ibe4300275286ef275b2097534c84f1029d761d87
- 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
This updates the camera module API to have vendor-specific tag support.
Vendor-specific metadata tags could be contained in static camera
characteristics, so we need a method of accessing vendor tag information
from the module level (and not just with a device open).
Bug: 10612133
Change-Id: I28e8c769f8112ff4f745f3f1b5472e8a718f1356
- Support a simple callback from camera HAL module to framework, to
indicate a change to module configuration or status.
- Add support for per-instance metadata to camera 2 device HAL.
Change-Id: I25699ff096c4f3578b9e54c7e6e60ce2449adc82
- High-level behavior is identical to device HAL 2.0
- Interface is cleaned up and simplified greatly
Change-Id: Ia867bbf9484be2256470f4acfab7fc3d47e408f4
Disallow modification to static characteristics structure, and clarify
ownership and lifetime of the structure.
Also update test code accordingly.
Bug: 6243944
Change-Id: I6921d6889937212867efb99aa3881ab3ffc4f6f9
Needs a third change that's not yet done with review.
This reverts commit c9ec8a656b59912f496880d3a63c0decd490f09d
Change-Id: Ic3e465e1308cbf107a250ec17b73a59a35e52f9f
Disallow modification to static characteristics structure, and clarify
ownership and lifetime of the structure.
Also update test code accordingly.
Bug: 6243944
Change-Id: Ib8de5e9d6580187b21a5ae9a28a3d24f1d083f7b
These constants should be used by HAL implementations to indicate
which versions of the module and device APIs they support.
Change-Id: I4b6eae278481545694e6a1827833b5958c26720c
