568e66ff9e
This change stores the period size (fraction of the pipe buffer size) in the submix device's configuration which is then used to calculate the input and output stream buffer size. In addition, accessors for the input / output stream format have been modified to use the pipe format in the device configuration rather than returning hard coded values. Bug: 11273000 Change-Id: I9c14f8d549f4b4a6d7f77a9aeab4edfa5ba6bd1a |
||
---|---|---|
.. | ||
audio | ||
audio_remote_submix | ||
camera | ||
consumerir | ||
fingerprint | ||
gralloc | ||
hwcomposer | ||
local_time | ||
mcu | ||
nfc | ||
nfc-nci | ||
power | ||
sensors | ||
tv_input | ||
usbaudio | ||
vibrator | ||
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 /system/libs/hw/ and have a well defined naming convention: /system/libs/hw/<*_HARDWARE_MODULE_ID>.<ro.product.board>.so /system/libs/hw/<*_HARDWARE_MODULE_ID>.<ro.board.platform>.so /system/libs/hw/<*_HARDWARE_MODULE_ID>.<ro.arch>.so /system/libs/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/.