- 17 Mar, 2015 1 commit
-
-
Ricardo Garcia authored
Creating a simple "stub" audio HAL to be used in systems with no hardware output. This stub HAL allows systems to run CTS tests and other audio system calls without crashing or unexpected behavior. The stub can be used also as a starting point for creating a new HAL. This is needed for audio_output feature support. bug: 19439530 Change-Id: I9e8e06e5b7fea7c7f3ff1de303db015b51e8acde
-
- 09 Mar, 2015 6 commits
-
-
Eino-Ville Talvala authored
-
Eino-Ville Talvala authored
-
Eino-Ville Talvala authored
Account for requirement to pass in dataspace in stream creation. Change-Id: Ibc5af912ef4a55b787c70843fc82422977a02c0b
-
Eino-Ville Talvala authored
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
-
Andres Morales authored
-
Andres Morales authored
Buffers will likely be bigger than 255! Change-Id: I8cc1ac1c656493a94e5a41ce6ee948af159f18f6
-
- 06 Mar, 2015 2 commits
-
-
Eino-Ville Talvala authored
-
Eino-Ville Talvala authored
- Replace RAW_SENSOR with RAW16 - Remove sRGB formats Change-Id: Ic5c44878c638c3d3559495ea5685e10fcc2c39e1
-
- 05 Mar, 2015 2 commits
-
-
Andre Eisenbach authored
am c7bea4fc: (-s ours) am a8d33714: (-s ours) DO NOT MERGE ANYWHERE Bluetooth native dumpsys logging support (1/4) * commit 'c7bea4fc': DO NOT MERGE ANYWHERE Bluetooth native dumpsys logging support (1/4)
-
Andre Eisenbach authored
* commit 'a8d33714': DO NOT MERGE ANYWHERE Bluetooth native dumpsys logging support (1/4)
-
- 04 Mar, 2015 1 commit
-
-
Andre Eisenbach authored
Bug: 18508263 Change-Id: Id7b69a6ed7d817a0f048cb8ebf0889c600171926
-
- 27 Feb, 2015 3 commits
-
-
Chien-Yu Chen authored
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
-
Shawn Willden authored
* commit '55eb5b0c': Separate keymaster0 and keymaster1 HALs.
-
Shawn Willden authored
* commit 'e05ffdbb': Separate keymaster0 and keymaster1 HALs.
-
- 26 Feb, 2015 5 commits
-
-
Shawn Willden authored
* commit '17dde875': Separate keymaster0 and keymaster1 HALs.
-
Shawn Willden authored
-
Shawn Willden authored
* commit 'ffaaf821': Separate keymaster0 and keymaster1 HALs.
-
Shawn Willden authored
For now the keymaster1 HAL still includes all of the keymaster0 entry points, and soft_keymaster_device will continue to implement them. In the near future the keymaster0 entry points will be removed, as soon as we can ensure that keystore no longer needs them. Change-Id: I5c54282c12d1c4b8b22ed4929b6e6c724a94ede4
-
Shawn Willden authored
For now the keymaster1 HAL still includes all of the keymaster0 entry points, and soft_keymaster_device will continue to implement them. In the near future the keymaster0 entry points will be removed, as soon as we can ensure that keystore no longer needs them. Change-Id: I5c54282c12d1c4b8b22ed4929b6e6c724a94ede4
-
- 24 Feb, 2015 5 commits
-
-
Shawn Willden authored
For now the keymaster1 HAL still includes all of the keymaster0 entry points, and soft_keymaster_device will continue to implement them. In the near future the keymaster0 entry points will be removed, as soon as we can ensure that keystore no longer needs them. Change-Id: I5c54282c12d1c4b8b22ed4929b6e6c724a94ede4
-
Alex Klyubin authored
* commit '8840a683': Clarify the meaning of KM_TAG_MAC_LENGTH.
-
Alex Klyubin authored
* commit '587d8313': Clarify the meaning of KM_TAG_MAC_LENGTH.
-
Alex Klyubin authored
* commit '4f5949b5': Clarify the meaning of KM_TAG_MAC_LENGTH.
-
Alex Klyubin authored
-
- 23 Feb, 2015 2 commits
-
-
Michael Wright authored
-
Michael Wright authored
Change-Id: Ia959dd1d1adf024459d2423fc9d59a811466e53c
-
- 21 Feb, 2015 1 commit
-
-
Alex Klyubin authored
Change-Id: I18478923059783e955613142a8d3352f98f5d7b0
-
- 20 Feb, 2015 4 commits
-
-
Paul McLean authored
Change-Id: I96954f883798f8e10adce56d9c33b70574999d1c
-
Paul McLean authored
Eliminated unnecessay locking/unlocking in adev_set_parameters(). Corrected and simplified lock/unlock order in out_write() and in_read(). Bugs 19363750 Change-Id: Iede9a95f5f17645d9780b344fd5ee009cd9fa94d
-
- 19 Feb, 2015 2 commits
-
-
Bill Yi authored
-
Chien-Yu Chen authored
-
- 18 Feb, 2015 6 commits
-
-
Paul McLean authored
-
Paul McLean authored
Also clean up logging. This doesn't completely fix the referenced bug, but substantially reduces the instances of long latency on USB device disconnect. Bug: 19363750 Change-Id: If0a6d64c4973277ae2474e121198e47df973965e
-
Shawn Willden authored
* commit '66b7b389': Added insecure (chunkless) AEAD option. Add additional param lists to update and finish.
-
Shawn Willden authored
* commit '0e5fca1c': Added insecure (chunkless) AEAD option. Add additional param lists to update and finish.
-
Shawn Willden authored
* changes: Added insecure (chunkless) AEAD option. Add additional param lists to update and finish.
-
Shawn Willden authored
* commit 'f18670b8': Rename KM_TAG_ADDITIONAL_DATA to KM_TAG_ASSOCIATED_DATA
-