| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| | |
Change-Id: Ia507a1378487640683985dbce2e76679261900d3
(cherry picked from commit 3eed99a54b55a120c835de63b5872121b2fe98d1)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rescoping was never a very good solution to the problem of supporting
multiple sets of authorizations for a given key material. For M we're
removing it and in the future a better solution will be provided.
Change-Id: I6f7585274487bd66e4d90e89014af41e9aa30411
(cherry picked from commit 7f10ab99fc63e99252d924b9e0bdfefef5374b40)
|
|/
|
|
|
| |
Change-Id: Ic6e7ad21cd3a253a38a6291bf08517c7e441af2b
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
LE low power extended scan feature header changes
based on Google spec v0.95
Bug: 20029342
Change-Id: Id1020a4da177d0bc421fdd123c5355a291cc0475
|
| |
| |
| |
| |
| | |
Bug: 20127433
Change-Id: I32eab62459003c526d3cf9ef108be7b2fd709960
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
MS-Assisted has only be supported for legacy reasons for a while now.
This change moves gps.h in a direction where MS-Based (on device
computation with AGPS/Supl support) is the preferred mode to compute
locations in the device.
Change-Id: Id34a84bae79be52a435b78d249fb5b86a5f6b090
|
| |
| |
| |
| |
| | |
Change-Id: If45ebc228425eaa43bf9abde934f8bb4e7d97e6c
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A property map holds the collection of the properties for a given
device identifier. HAL modules allocate and release these property maps
to control the lifetime of the data. The host will typically open and
read the corresponding idc file on allocation, and release these
resources when it is freed.
Change-Id: Ia13ec7b7abf1a79eeed87dc744c174a37f1fb8a9
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For use by Camera HAL libraries to perform one-time initialization
steps after the library is loaded.
Bug: 20016050
Change-Id: Ia01ae0eafcadece9124ac2cfcc3b1c3939352843
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Custom sensors should not be included in sensors.h
Change-Id: I553fbe3dd41eaaa70628184f5a0b9499699f17bc
|
|\ \ \ \
| |/ / /
|/| | /
| | |/
| |/| |
9a92a7b L2CAP and SDP Search API for BT profiles (1/2)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Added interface to create SDP records, to allow the upper
layers to set the content of the SDP record, including
both a RCFOMM channel and a l2cap PSM.
Change-Id: I7c47848a10b3d3091afbeadb4de8a8d7ea812288
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
* commit '7ff6445c7ae2c1f66dda17f5a5ee5ba53f23d796':
HWC 1.5: Add per-layer damage region
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This adds an array of rects to hwc_layer_1_t that define which
portions of that layer's source buffer have been modified. If there
are a non-zero number of rects, then any portion of the source buffer
not touched by one of the rects may safely be assumed to not have
been modified. If no rects are defined, then the whole source buffer
must be assumed to have been modified.
Change-Id: Id5efafee74602ed7d76609180e334ed203c23f7e
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Measurements interface. b/19938206"
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
interface.
b/19938206
Change-Id: I9dc863e9333507d5603eee3951b0a2b7c8c2b299
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Change-Id: Ied10a03213b8473b1a625229a75b7af6126d635a
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Adding HAL changes for the following
i) a method to place the HAL in a special mode.
Expect to use this method for data-injection.
ii) a method to inject sensor data into the sensors subsystem.
iii) New sensor type for a SYNC event (google custom sensor).
iv) New sensor type for a nudge gesture (google custom sensor).
Change-Id: Idf0479b6301c5363cf51938e23aabc790b69fa96
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
b/19938206
The changes have been worked out after working with two partners to implement the interface.
The need of the additional flag is required, given that each partner can only provide one type of
pseudorange rate (corrected vs uncorrected).
Change-Id: I2d3bdffe5c24f8df97b33111a6753cc7b0f2b3d9
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | / / /
| | |/ / /
| |/| | | |
* commit '6c93927dd390abcf0e6254a38ef2c0f14fc1a51e':
Add KM_ORIGIN_UNKNOWN.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This designates keys whose origin cannot be determined because the
keymaster implementation is old and did not record it.
Change-Id: I3c366d527ed211c59f6dc04ddb48f3e9b3a07c7d
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Currently GmsCore has to guess how many locations to retrieve
based on requested frequency and then demux the output looking
for timestamps (that aren't monotonically increasing). This
capability gives GmsCore a more graceful solution.
Change-Id: If2d054c09efc98e33e357796bbfcd37c91b24ec8
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
-Allows GmsCore to know if location batching is
unsuccessful so it can switch to a SW solution.
Change-Id: I5a01d44fdcf6daa07d6b40cf95a674e98179bf00
|
|\ \ \ \ \ |
|
| | |/ / /
| |/| | |
| | | | |
| | | | | |
Change-Id: I93ebdbdaf7dc0b2ddf1a7e7a089073db51cd15c3
|
|\ \ \ \ \
| | |/ / /
| |/| | |
| | | | |
| | | | | |
* commit '9e4985e8cb40e6e53a01a1080c210c0c09be305f':
hw_auth_token: make timestamp 64 bits
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I1f871300cd2edb407479e1e38284b068db364b38
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: Ic01da2b9ed8efcdba7750d8ca7fe2321d9047b68
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Change-Id: Iffd250233c9ec2a28682f018984e28531bd83e7a
|
|\ \ \ \ \ \ |
|
| |\ \ \ \ \ \
| | | |_|_|_|/
| | |/| | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Fix for signed value in onlost/onfound
Bug: 19891550
Change-Id: Idee4c566fe0d6f10a87c92f5bf03743fddbe2261
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Bug: 19609671
Change-Id: Id28e188159aa41c940723fb5b12cade0a48e506b
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Also clarify rotation field has no meaning and will always be 0
for a input stream.
Change-Id: I0f4343a0bfa7bf09ba887c78a1da1c08daa35333
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Bug: 19186859
Change-Id: Ie051f966a758c68d354250c245a87df57a4f4ae3
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Also bump the HAL version to 3.3 for reprocessing spec update
Change-Id: I37eda90970eace23c42ba9106d4db1587df8d1b4
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Update camera module API 2.4 for usb camera support.
Change-Id: Id8329e31ad0622bdc06c60e87e97c742a9719b3b
|