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
* /data/tombstones and /data/vendor/tombstones are both created by
the system's init.rc.
* Creating /tombstones at the root isn't allowed since the root is
a ramdisk and mounted read-only.
Change-Id: I6c3a287056a2264d9e9ffe4557ecca8c6e03c0bb
CAF replaced rate_limit_us with up_rate_limit_us and
down_rate_limit_us in msm-4.9 kernel with commit:
"ANDROID: cpufreq: schedutil: add up/down frequency transition rate limits"
ref: a37cf5fe1a
Therefore, update the node in init.qcom.power.rc as well.
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
Change-Id: I26c846d7885b5308d5f8a86e7a9b43cdb6346610
Currently streaming_maxburst is set to 1 for UVC. Increase it
to 10 to get better throughput numbers for UVC.
Change-Id: I76458cca14953179c65119032bcba401dd8d4929
Add required changes to add support for 1080p and 4K MJPEG format.
Also fix wHeight issue for UVC streaming, else streaming won't work
for 720p resolution.
Change-Id: Ie2b911e5940babe58156dc84df4415b34d2a7103
If the sys.usb.state is set to any other value other than
rndis(rndis,adb) when tethering is enabled through UI, the
USB device manager falls back to the default or previous
composition.
If a RNDIS is enabled with along with other debug functions
using the persist.vendor.usb.config.extra, set the
sys.usb.state to rndis(rndis,adb) irrespective of the config
that is being enabled to prevent the fallback.
Change-Id: Ib4e120895e62fc14ac11941b6b46cc7f0460ede8
The following SELinux denials are seen when booting into charger mode:
type=1400 audit(1746.159:22): avc: denied { dac_read_search } for
comm="init.qcom.usb.s" capability=2 scontext=u:r:vendor_qti_init_shell:s0
tcontext=u:r:vendor_qti_init_shell:s0 tclass=capability permissive=0
type=1400 audit(1746.159:23): avc: denied { dac_override } for
comm="init.qcom.usb.s" capability=1 scontext=u:r:vendor_qti_init_shell:s0
tcontext=u:r:vendor_qti_init_shell:s0 tclass=capability permissive=0
type=1400 audit(1746.267:24): avc: denied { dac_read_search } for
comm="init.qcom.usb.s" capability=2 scontext=u:r:vendor_qti_init_shell:s0
tcontext=u:r:vendor_qti_init_shell:s0 tclass=capability permissive=0
type=1400 audit(1746.267:25): avc: denied { dac_override } for
comm="init.qcom.usb.s" capability=1 scontext=u:r:vendor_qti_init_shell:s0
tcontext=u:r:vendor_qti_init_shell:s0 tclass=capability permissive=0
The DAC errors indicate that there is some kind of access, usually
by root, to a file or directory where the ownership is given to another
user/group which is not root. So since root may not have explicit
permission to access it has to override the default access control
which is flagged by SELinux.
In charger mode, like in normal boot, the init.qcom.usb.sh script
executes in the same process as init, so it is executing as root.
The script is trying to read/write to the ConfigFS string entries.
The fix for these denials is to ensure that any files/directories
being accessed by the script give root permission to access the same.
Hence remove the shell/shell ownership change when creating the USB
gadget and config subdirectories in ConfigFS.
While at it also remove mounting of ADB FFS and the ConfigFS function
instance as we are not enabling ADB in charger mode.
Change-Id: I33d6a9ce8e1bb4594a053156d46688ab11c5491d
On some targets (such as GKI) the default bMaxPower is not able to be
hard-coded using the kernel config USB_GADGET_VBUS_DRAW. Instead we can
set this value via USB ConfigFS.
Change-Id: I467dab4fa85e7d07837f6afb6d58c73812619022
This change adds rules to move usage of USB MTP/PTP functionality
with USB F_FS driver instead of F_MTP/F_PTP drivers. It selects
functionfs based MTP/PTP functionality based on vendor.usb.use_ffs_mtp
property value. Set vendor.usb.use_ffs_mtp to true for Lahaina platform.
sys.usb.mtp.device_type is used by MTP server to provide perceived
device type information to host. Use correct sys.usb.mtp.device_type
property and set value 3 ( 2 - media player and 3 - Mobile handset).
Change-Id: I005bfea4babef012e331dcc4999e5e6af6465b6e
Remove obsolete android_usb based property triggers now
that configfs is always used. Merge in init.msm.configfs.rc
so we now have just a single .rc init file.
Also remove all other references to /sys/class/android_usb/*.
Change-Id: I06eba8e715ccee5974dc9de8ac19df6c79ae0c45
Directly execute the init.qcom.usb.sh helper in the 'on boot'
and 'on charger' actions rather than spawning it as a oneshot
service. After that, directly update sys.usb.config with the
from persist.vendor.usb.config. This streamlines and guarantees
it will execute synchronously which can help avoid rare race
conditions with other USB property triggers that could execute
in parallel.
Change-Id: Iaf798b146d071b11857a4cf54fbaf7ae0d5d2431
Create configFS entries for two additional diag instances
and mount their respective FunctionFS paths. The diag-router
app will read/write to these for MDM and WLAN instances,
respectively.
Change-Id: Icc896f19a76e7d154e5b9b9a2f1bfc422a3e47e3
With support now for diag-router using USB FFS driver, the kernel
driver is no longer going to automatically update the DLOAD IMEM
with the required PID/Serial information that is used when the device
transitions into crash download mode so that a port re-enumeration
is avoided. In order to pass the same PID/Serial information, the
same kernel driver now exposes configfs attributes that userspace
can write. Hence the serial number can be written once during "on
boot", and likewise the PID can be updated whenever a composition
is selected that contains Diag as the first interface.
Change-Id: I45d52ecd30fcc4978c9bb4fbe9caa75e12c0b860
Support Diag over USB using F_FS driver by instantiating "ffs.diag"
ConfigFS instance and mounting the functionfs path for the same.
Introduce a new property 'vendor.usb.diag.func.name' which is used
to distinguish between FFS and legacy f_diag and update all Diag-
enabled compositions accordingly.
The `vendor.usb.diag.func.name` property can be overridden on
a per-target basis simply by adding the key=value to the
PRODUCT_PROPERTY_OVERRIDES build variable. This gets generated
into the /vendor/build.prop which overrides the default value of
'diag' set in /vendor/default.prop.
Change-Id: I005a441b39697b489bcd8d74b5cb26fb3b47fdf7
There's nothing really that different here when compared to the
common HAL except for the specific DT2W handling, which can simply
be supported as a power feature lib.
Change-Id: I4c9c2530c8090e05dab38ed829d59ece5e00e1fb
During bootup the device first enumerates in ADB only composition
and then falls back to the persist.sys.usb.config.
Prevent this enumeration in ADB only composition during bootup
by setting the sys.usb.configfs from init.qcom.usb.rc
Change-Id: I6c93a778cc0decc6b5c256c60734b0597d753a9d
0x9020 composition includes DIAG + ADB + DUN + NMEA. Add support
for the same.
Change-Id: I364d4e87b63d7e5dfb394db6e92e650764b7cc96
Signed-off-by: Ajay Agarwal <ajaya@codeaurora.org>
Set sys.usb.configfs property when vendor.usb.configfs is set.
This prevents two enumerations at boot up. First one is done
when system core init enumerates with adb only composition. Soon
after this vendor default usb composition switch happens. Sometimes
controller fails to halt in the middle of control transfers when run
stop bit is cleared to perform composition switch to initiate second
enumeration. This is resulting in to device enumeration SET ADDRESS
failure as controller stops accepting SETUP packet from Host.
Change-Id: I5a4840d8eedf59809cc4d158f95d35f0477830bb
On some targets, QDSS can be used over SW path. This change
adds an property for QDSS instance name which will be defined
for each target in target.rc file. That property can be changed
accordingly for targets which uses QDSS over BAM or SW.
Change-Id: Ibf9af45f20feb7434d15b02ff86c91fce914dbd2
/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 iuicc device that can be opened by spdaemon to create
iuicc channel and interact with iuicc application on the
Secure Processor
Change-Id: I2c37053a9e7445abfe4f0c11868277bbf133266a
- Grant SYS_NICE capabilities to audio HAL processes as sound trigger
HAL threads need to run at real time priority as well as use the
CPU affinity, for far field voice.
CRs-Fixed: 2359951
Change-Id: Ie0da744978609c750e92aec2c6001ace1868ad31
As part of this FR we are moving vendor data specific module
configurations to custom vendor data init rc files
Change-Id: I64e839c2b0fbd0826fe79b95259af2a10e8b1ea1
