tequilaOS/platform_hardware_libhardware
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
platform_hardware_libhardware/modules
History
Jean-Michel Trivi eec87706d2 Remote audio submix: blocking writes and sleeping reads. 
Change how the remote audio submix is handling piping audio
 through the pipe:
 - use a MonoPipe as audio sink for blocking writes,
 - use a MonoPipeReader as audio source for non blocking reads,
  and keep track of when recording started to align the
  time at which the in_read() call should return with the
  projected time of the recording duration.

Change-Id: I8b0f8c56a0486806101e272dfbf9c6d2d1c11112
2012-09-17 09:59:42 -07:00
..
audio audio: new audio devices enums 2012-09-07 10:32:57 -07:00
audio_remote_submix Remote audio submix: blocking writes and sleeping reads. 2012-09-17 09:59:42 -07:00
gralloc am 8405fe5a: am 1fbbb08d: Merge "remove seemed useless gralloc_open() call in fb_device_open()" 2012-06-12 15:18:23 -07:00
hwcomposer Add multi-display and flip fence to HWC 2012-08-07 12:26:59 -07:00
local_time Modifications to audio_hal for Android@Home. 2012-02-10 08:58:32 -08:00
nfc Initial NFC HAL for NCI controllers. 2012-09-14 13:56:58 -07:00
nfc-nci Initial NFC HAL for NCI controllers. 2012-09-14 13:56:58 -07:00
power remove triggering suspend from power hal 2012-05-03 19:01:02 -07:00
usbaudio audio: new audio devices enums 2012-09-07 10:32:57 -07:00
Android.mk Initial NFC HAL for NCI controllers. 2012-09-14 13:56:58 -07:00
README.android auto import from //depot/cupcake/@135843 2009-03-03 19:32:14 -08:00

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/.