Evolution-X-Tensor/device_google_zuma
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Start storageproxyd earlier, but after /dev/sg1 has arrived.

Browse source 
Background:
* Sometimes /dev/sg1 isn't ready when storageproxy attempts to start.
  Add a trigger to wait for the device.

Bug: 245194332
Bug: 245724566
Test: manual
Change-Id: I23300b7f1a0170dc1b73c5e3b5b2c7e2b1ecba2b
This commit is contained in:
Mike McTernan 2022-09-08 14:03:18 +01:00
parent 22f83ce4da
commit 27fc7b2c2d
1 changed files with 5 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
conf/init.zuma.rc
View file

@ -318,6 +318,11 @@ on init
write /sys/class/devfreq/gs_memlat_devfreq:devfreq_mif_cpu6_memlat@17000010/mem_latency/ratio_ceil 3200
write /sys/class/devfreq/gs_memlat_devfreq:devfreq_mif_cpu7_memlat@17000010/mem_latency/ratio_ceil 3200
on post-fs
# Ensure device is ready and start storageproxyd
wait /dev/sg1
start storageproxyd
on late-fs
# Wait for keymaster HALs
exec_start wait_for_keymaster