Files
device_google_redfin/init.recovery.device.rc
Mark Salyzyn 4507caba1c fastboot/recovery: wait for display
With GKI we find in certain situations the timing of the drivers
loading is delayed as compared to a monolithic kernel.  This
introduces a race where during second stage init, the attributes
inside /sys/bus/platform/drivers/drm_dsi_ctrl might not be set by
the time the menu is painted on the screen.

To address this, we wait for /sys/class/drm/card0 to instantiate.

Signed-off-by: Mark Salyzyn <salyzyn@google.com>
Bug: 151950334
Test: make sure user space fastbootd comes up reliably for a GKI kernel
Change-Id: I64c21529c21cdd8c8ad9908c8a57e933549986a5
2020-06-02 18:49:44 +08:00

19 lines
709 B
Plaintext

on fs
wait /dev/block/platform/soc/${ro.boot.bootdevice}
symlink /dev/block/platform/soc/${ro.boot.bootdevice} /dev/block/bootdevice
on init
setprop sys.usb.configfs 1
# Don't lose recovery logs- keep warm reset for coming out of recovery.
write /sys/module/msm_poweroff/parameters/warm_reset 1
# Enable thermal mitigation
write /sys/devices/virtual/thermal/tz-by-name/backup-charge/mode enabled
# Block layer tuning: discard chunk size up to 128MB
# Otherwise, contiguous discards can be merged
write /sys/block/sda/queue/discard_max_bytes 134217728
on early-init
# Wait to make sure we do not try to talk too early to the display
wait /sys/class/drm/card0