This addresses an underlying problem since /dev/hw_random is used. The
issue is that EntropyMixer, which runs in system_server, needs to read
from /dev/hw_random, but thanks to our qualcomm ueventd, EntropyMixer
can never accress this node, resulting in warnings like this:
W EntropyMixer: Failed to add HW RNG output to entropy pool
W EntropyMixer: java.io.FileNotFoundException: /dev/hw_random (Permission denied)
AOSP ueventd handles this well, so just remove this line to get things
back to stage. This issue was never exposed because Google derps the
logging here, which is already fixed on Pie.
c78a463e87
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
/dev/wigig_sensing is the entry point to an SPI kernel driver which is a
part of a remote sensing solution using 60GHz HW.
Change-Id: I1b538e0c58ae784997407f91a7647c2188ee7d58
/dev_sp_nvm is used by sp_iar_lib to store CMAC values for spu
firmware and application
Change-Id: I2ac5f29b66448a526cdbc6a1ccefd5f80066c170
Signed-off-by: Li Li <liil1@codeaurora.org>
Add iuicc0 and iuicc1 devices that can be opened
by spdaemon to create iuicc0 and iuicc1 channels
respectively and interact with iuicc0 and iuicc1
applications respectively on the Secure Processor.
Change-Id: I2554616073553065416756e23c3e27f2f9c90021
Grant capabilities and change file permissions to allow the sensors.qcom
daemon to start up as the system user/group, rather than running as
root.
Fixes: 63775281
Test: monitor logcat after reboot, confirm no file open errors. Run
QSensorTest, confirm all sensors provide sane data. Confirm that
IMU calibration can read + write its saved settings. Run sensors CTS.
Change-Id: Ib80ea21900d6af6cd34c82c4a63f50c7e0ac18ff
To support end-to-end DRM content playback with SG List feature,
android.hardware.drm@1.0-service needs to have access permission
to /dev/qce to map & unmap ION buffer virtual address with HW Crypto
Engine. So, set /dev/qce device permission 0660 and let it be
accessible by user "system" and group "drmrpc".
Change-Id: If9c0ed70acc2bb063344692374f51441fe84eff6
To support ODL to read data from QDSS, create a custom group
and set permission of byte-cntr device. And also set
permission to coresight-tmc-etr/block_size to enable
byte-cntr feature.
Change-Id: Ic80156667dd7511392d5970ddcbd0fdc43ffffca
Signed-off-by: Saranya Chidura <schidura@codeaurora.org>
This addresses an underlying problem since /dev/hw_random is used. The
issue is that EntropyMixer, which runs in system_server, needs to read
from /dev/hw_random, but thanks to our qualcomm ueventd, EntropyMixer
can never accress this node, resulting in warnings like this:
W EntropyMixer: Failed to add HW RNG output to entropy pool
W EntropyMixer: java.io.FileNotFoundException: /dev/hw_random (Permission denied)
AOSP ueventd handles this well, so just remove this line to get things
back to stage. This issue was never exposed because Google derps the
logging here, which is already fixed on Pie.
c78a463e87
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
To support end-to-end DRM content playback with SG List feature,
android.hardware.drm@1.0-service needs to have access permission
to /dev/qce to map & unmap ION buffer virtual address with HW Crypto
Engine. So, set /dev/qce device permission 0660 and let it be
accessible by user "system" and group "drmrpc".
Change-Id: If9c0ed70acc2bb063344692374f51441fe84eff6
To support ODL to read data from QDSS, create a custom group
and set permission of byte-cntr device. And also set
permission to coresight-tmc-etr/block_size to enable
byte-cntr feature.
Change-Id: Ic80156667dd7511392d5970ddcbd0fdc43ffffca
Signed-off-by: Saranya Chidura <schidura@codeaurora.org>
This addresses an underlying problem since /dev/hw_random is used. The
issue is that EntropyMixer, which runs in system_server, needs to read
from /dev/hw_random, but thanks to our qualcomm ueventd, EntropyMixer
can never accress this node, resulting in warnings like this:
W EntropyMixer: Failed to add HW RNG output to entropy pool
W EntropyMixer: java.io.FileNotFoundException: /dev/hw_random (Permission denied)
AOSP ueventd handles this well, so just remove this line to get things
back to stage. This issue was never exposed because Google derps the
logging here, which is already fixed on Pie.
c78a463e87
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
