f14a550e7d
Adds sensor direct report mode support to multihal. Limited by hal API only the first HAL in configuration list can support sensor direct report. Sensor operation parameter support in multihal module is added in this CL. In treblized device multihal is enabled by default and implementation is included in default implementation. Remove multihal shared lib generation in device specified PRODUCT_FULL_TREBLE. Test: warning message shows up on device that specified both PRODUCT_FULL_TREBLE and USE_SENSOR_MULTI_HAL flags. Test: cts test passes Change-Id: I868e7c1ce727370b333f80bbfe737fb106f6d106 |
||
---|---|---|
.. | ||
audio | ||
audio_remote_submix | ||
camera | ||
consumerir | ||
fingerprint | ||
gralloc | ||
hwcomposer | ||
input | ||
local_time | ||
nfc | ||
nfc-nci | ||
power | ||
radio | ||
sensors | ||
soundtrigger | ||
thermal | ||
tv_input | ||
usbaudio | ||
usbcamera | ||
vehicle | ||
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/.