This is required so Lyric is able to talk to smfc driver
Bug: 257084044
Test: ls -la /dev/video12 shows proper file permissions
Change-Id: I181c8f8d1647d91d092d83887f28bef640e3b464
To support input device lights manager feature in frameworks, provide
sysfs node access to system server process.
DD: go/pk_backlight_control (For keyboard backlight control for external
keyboards)
Kernel provides a standardized LED interface to expose LED controls
over sysfs: https://docs.kernel.org/leds/leds-class.html
The feature will be provided for devices with kernel sysfs class led
support and vendor kernel driver for input controllers that do have
lights. The kernel sysfs class led support is a kernel config option
(LEDS_CLASS), and an input device driver will create the sysfs class
node interface.
By giving system_server the access to these sysfs nodes, the feature
will work on devices with the kernel option and kernel input/hid driver
support. We do use CTS tests to enforce the kernel options and the
input device drivers.
What's already supported:
- We already expose paths for UHID based LED nodes which covers all
bluetooth based peripherals that have custom vendor drivers to expose
LED sysfs nodes. (see CL aosp/1546377)
What's included in this CL:
- Exposing paths for sysfs nodes for external USB based devices that
expose LED nodes using vendor specific drivers using standard LED
interface provided by Kernel
- We are using specific paths for USB devices instead of
/sys/class/leds to avoid giving access to system LED nodes that would
also appear under /sys/class/leds (see discussion in aosp/1546377)
NOTE: Light HAL should never touch the HID device sysfs light, as the
light HAL only defines a number of lights supported
(https://android.googlesource.com/platform/hardware/interfaces/+/master/light/2.0/types.hal)
but not include input device lights, so we shouldn't have conflict
for managing these lights.
NOTE: External keyboard backlight is different for HAL light type
KEYBOARD which is for devices with attached keyboards.
Test: manual
Bug: 245506418
Change-Id: I2e9f3cbce55f3f894ca346bafa5ded280086a3ca
Bug: 195964858
Test: Paired a Sony PS4 controller and verified that it's discovered by
the dynamic sensor HAL.
Test: See details in testing done comment in
https://googleplex-android-review.git.corp.google.com/15847274 .
Change-Id: I8d5987171d5b316410e8ba34cc02a4d4508e0054
Enable the FP HAL to read from the mfg_data partition chowning to system
Bug: 193549276
Test: sideload cal with valid signature. auth. enroll.
Change-Id: I0897e545dc368782587ae031716012a806d05485
Specify ownership to system and r/w permissions to user/group.
Allows dumpstate to access /dev/trusty-log0.
Bug: 188285071
Test: lshal debug android.hardware.dumpstate@1.1::IDumpstateDevice/default trusty
Change-Id: I935cb9dd11d1e0968ab0e2c9d7349de336502e7c
Set the permission for the two dma heap.
They are used for mmap audio in exclusive mode.
/dev/dma_heap/aaudio_playback_heap
/dev/dma_heap/aaudio_capture_heap
Bug: 165737390
Test: make
Change-Id: Ie8d35d59fb3bde10915dd0e0746852849acbad8c
Set /dev/acd-audio_dcdoff_ref as 0660 system audio
crw-rw---- 1 system audio u:object_r:aoc_device:s0 500, 29 2021-03-18 22:19 /dev/acd-audio_dcdoff_ref
Bug: 180984363
Bug: 165719427
Test: make -j128
Test: ls -alZ /dev/acd-audio_dcdoff_ref
Change-Id: I4720349eccd5e3b797ff8e964329fe6352d5bba0
Revert of the following changes:
I70af757f5 conf: change a group about dma_heap for video codec
Id4fc2f04b uses dmabufheap on codec2
I090f0491f disable to use BLOB allocator
Bug: 182312949
Test: boot without DMABUF failures
Change-Id: Ibeb05a1341c15a206b8c1d2b9c9765769f6472e1
