e72761731d
This applies to the following types: - audio_gain_mode_t; - audio_flags_mask_t; - audio_channel_representation_t; - audio_channel_mask_t; - audio_devices_t. Enum types are distinct thus proper overloading on the type is possible in C++. Also, assignments to enum types are less prone to errors. Bug: 169889714 Test: basic audio functionality Change-Id: I8f1e6fa2bbad8900fdae66f01ac70c75953fd62c Merged-In: I8f1e6fa2bbad8900fdae66f01ac70c75953fd62c |
||
---|---|---|
.. | ||
audio | ||
audio_remote_submix | ||
camera | ||
consumerir | ||
fingerprint | ||
gralloc | ||
hwcomposer | ||
input/evdev | ||
local_time | ||
nfc | ||
nfc-nci | ||
power | ||
radio | ||
sensors | ||
soundtrigger | ||
thermal | ||
tv_input | ||
usbaudio | ||
usbcamera | ||
vibrator | ||
vr | ||
Android.mk | ||
README.android |
Default (and possibly architecture dependents) HAL modules go here. libhardware.so eventually should contain *just* the HAL hub (hardware.c), everything in it should be rewritten as modules. Modules are .so in /vendor/lib/hw/ and have a well defined naming convention: /vendor/lib/hw/<*_HARDWARE_MODULE_ID>.<ro.product.board>.so /vendor/lib/hw/<*_HARDWARE_MODULE_ID>.<ro.board.platform>.so /vendor/lib/hw/<*_HARDWARE_MODULE_ID>.<ro.arch>.so /vendor/lib/hw/<*_HARDWARE_MODULE_ID>.default.so They also have a well defined interface which lives in include/hardware/. A module can have several variants: "default", "arch" and "board", and they're loaded in the "board", "arch" and "default" order. The source code for the "board" variant, usually lives under partners/... The source code for "default" and "arch" would usually live under hardware/modules/.