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
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
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
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
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
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
To match the public API, seperate camera device in use and other
resources in use errors.
Bug: 2682206
Change-Id: Ie0451931f0c84fc65f3f6294a9f44bec10627afe
At the moment this is to accommodate associated data for AEAD modes, but
there may be other parameters in the future.
Change-Id: Ib94f3606e3f714f6fa75bf0d4bd75804d9a8db4e
Adds a new sensor type for converting the Android Wear defined wrist
tilt sensor type into an official android sensor type.
Change-Id: If6357aeb463a556a68a19b28931edec04f99a952
Rather than requiring implementations to be able to predict output
sizes, we'll just have the Java layer make a very conservative guess.
Change-Id: I4ef53a09d122d4ecf0c80b9dadc9c7a9073561cc
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
INPUT stream is not used by framework-implemented ZSL (HAL3.2), the sample
use case description is incorrect.
Bug: 19197776
Change-Id: I247ad8755b2197c2a62cc109c151749b42a4bd49
Change the boolean KM_TAG_SINGLE_USE_PER_BOOT to an integer-valued
KM_TAG_USES_PER_BOOT. This makes it more flexible without changing
implementation complexity.
Remove KM_TAG_RESCOPE_AUTH_TIMEOUT because there's no clear use case and
it seems unnecessarily complex.
Change-Id: Iad1512f5cc80f517e5ea7622288179c162bed2ad
Added a flag to pass system language information to HAL so that it can
respond to <Get Menu Language> in standby mode.
Bug: 19054079
Change-Id: Iada00307202f5c9429944184b62b6456b624125a
When a client requests to update the LE transport MTU, the server
currently does not get notified and can therefor not properly size
notifications appropriate to the current MTU.
Bug: 18388114
Change-Id: I136f32cba48da3302e13fb9a9ec81b8e01712138
Adds the setFeature callback which could be used to enable/disable
power as well as performance specific features.
POWER_FEATURE_DOUBLE_TAP_WAKE is added which uses the setFeature
callback to enable/disable the double-tap feature.
Bug: 16875464
Change-Id: I5ed9b5be8fddedf9861eedd962def421d9fac5bf
The HW A/V sync ID is retrieved from the HAL by calling
global get_parameters() with key AUDIO_PARAMETER_HW_AV_SYNC.
After the output stream is opened, the HW A/V sync ID is communicated
by stream set_parameters() with key AUDIO_PARAMETER_STREAM_HW_AV_SYNC.
Bug: 17112525.
Change-Id: Id1e3a3aa1e88d15461a609b381ca8c1902735a29
i) on-change sensors should set maxDelay.
ii) Drivers should hold a wake_lock till poll() is called
the next time when delivering events from wake-up sensors.
Change-Id: I4b137843d5c857f04601618548306a710fbfbe5c
Pass device address (and audio source for inputs) to
open_output_stream() and open_input_stream() audio HAL functions.
Bug: 14815883.
Change-Id: I5535677db3f3027917a31a7ed5c0a4c6bc013639
This reverts commit 0e956a7cd2dee76b762320c141960ffdb64d24eb.
The decision was to revert to the old behavior where retransmission
will be handled by HAL for efficiency.
Change-Id: If165b60c0408ea1015b83806f6bf21e18b15bc7f
This HAL was intended to support doze mode but it is currently
unused and it's best for it to stay that way.
Bug: 16516536
Change-Id: I4f442e27d68f18ff322afd4c1debd2f392687e80
On many devices, hardware cursors have stricter layout constraints than
other overlays. GRALLOC_USAGE_CURSOR indicates a buffer may be used as
a cursor; byte order and padding should be chosen accordingly.
GRALLOC_USAGE_CURSOR must not cause allocation failure. If the requested
properties (dimensions, format, other usage flags, etc.) aren't compatible with
the device's cursor hardware, the implementation must allocate the buffer
anyway, acting as if GRALLOC_USAGE_CURSOR were not specified.
Change-Id: I7d66e8d7c953421d996c5def3257d408f91962f4
Signed-off-by: Greg Hackmann <ghackmann@google.com>
Reorder hardware types so that older types comes first roughly. This
would make it more natural to add newer hardware types as they come.
In addition, remove verbose comments where the meaning is obvious from
the name.
Change-Id: I275e9e608c8c2392e3f7ec2c5d81743059f2d36b
Adds two functions to the HWC interface: one for querying the current
display configuration, and one for setting a new configuration. This
will enable DisplayManager to change the mode on demand.
Bug: 14320401
Change-Id: I556c509192b877b38b2103a78f937b3687f35546
Renamed various terms like, port, port_num to port_id, and
added a description that the id starts from 1.
Change-Id: I9229edff7fd75dd15e672e309369e237ca339238
New start_recognition() prototype with recognition
configuration structure specifying:
- List of keyphrases to listen to.
- Recognition mode for each keyphrase
- List of users and min confidence levels for each users
New recognition event format with confidence level and user ID
for each user.
Bug: 12378680.
Change-Id: I95e998c735321ceb5c27f477d894b574a6eca860
Removes tx_status event type which turns out not in actual use.
This changes makes send_message() work in sychrnonous fashion
when called by HdmiControlService. HdmiControlService has io thread
dedicated to interact with HAL, hence no need to introduce
another async flow for HAL.
Change-Id: I8ae21b1149cd36bfd0f9da215c4f23b30f0c8d30
This change introduces two new callbacks for applications to better
handle LE notification flow control and transport congestion. The
notification callback is invoked when the remote platform confirms an
indication or when a local notification has been passed to the
controller. No new notifications should be sent until a callback is
received.
Congestion callbacks are triggered when a GATT operation cannot be sent
to the local Bluetooth controller. Repeatedly calling
writeCharacteristic() for example will eventually trigger a congestion
callback. Applications cannot send additional data until a further
callback is received, indicating that the congestion has cleared up.
Change-Id: I613cbf968770921f853a407888bb8308849039f3
Both use the same structs for APIs and callbacks, but now
source and sink mode can operate independently with separate
Bluetooth profile services in the framework.
An extra callback btav_audio_config_callback is used for reporting
audio configuration for A2DP sink role
Change-Id: I6e8172b66ff95e61721d1c35790609b7ae2be030
This allows us to add a new BluetoothProfile subclass for
the AVRCP controller role independent of the existing AVRCP target support.
Change-Id: I504bbf58a88808d1a884266992ae0c635c62aca1
Since bluedroid is running outside of system_server, it does not have
the necessary Linux capabilities or filesystem permissions to access
/sys/power/wake_* and /dev/alarm (or any other wake alarm). This change
provides a mechanism by which bluedroid can call back up into Java code
and use the standard Android APIs to get wake locks / wake alarms.
Change-Id: I714fd394224d38da5ff0f82de5559599d522010b
Conflicts:
include/hardware/bluetooth.h
The blank HWC call is being replaced by a setPowerMode() call.
This incorporates all of the blank functionality, but provides added
support for display low power modes, if they are available in hardware.
Currently there are three supported modes:
- HWC_POWER_MODE_OFF : Turn screen off.
- HWC_POWER_MODE_DOZE : Put screen in low power mode.
- HWC_POWER_MODE_NORMAL : Turn screen on, and exit low power mode (if
display was previously in low power mode).
Where applicable, the device driver is expected to retain and restore
the low power mode state of the display during entry and exit from
suspend, respectively.
Bug: 13472578
Change-Id: I743ea3a2cb58247d14d7c47158b09a5309cca710
Signed-off-by: Prashant Malani <pmalani@google.com>
The size of hwc_layer_1_t varies depending on whether we're building
for a 32- or 64-bit target. This change splits the padding into two
sections so that we can add more fields without changing the overall
size on either bitness.
Change-Id: Ib7c960a9feb0061586dc6398211d7d3dc012d573
