diff --git a/kernel/configs/omamobile.config b/kernel/configs/omamobile.config index 4ba602d8a..598d814b2 100644 --- a/kernel/configs/omamobile.config +++ b/kernel/configs/omamobile.config @@ -151,6 +151,10 @@ CONFIG_DRM_GS_DECON=m # only to its compatible, and the thermal driver only reads. CONFIG_DRM_PANEL_GOOGLE_TG4C=m CONFIG_GS101_ACPM_THERMAL=m +# The Pixel 8 Pro's panel (HK3, kernel #160): brightness and 60/120 Hz +# through gs-dsim-cmd. A module that binds only to its compatible; until #160 +# lands, olddefconfig drops the unknown symbol. +CONFIG_DRM_PANEL_GOOGLE_HK3=m # Fingerprint bring-up (device/cheetah/FINGERPRINT-RESEARCH.md): Google's # Trusty driver (/dev/trusty-ipc-dev0), the Goodix sensor control device diff --git a/packages/omamobile-device-husky/README.md b/packages/omamobile-device-husky/README.md index 8a29247b4..8ee66050b 100644 --- a/packages/omamobile-device-husky/README.md +++ b/packages/omamobile-device-husky/README.md @@ -8,6 +8,8 @@ Omarchy Mobile's first userspace package for the Google Pixel 8 Pro (codename hu | `vendor/systemd/network/20-usb-gadget.network` | `/usr/lib/systemd/network` | Sets usb0 to 172.16.42.1/24 after handover. A replug may need a reboot: this package does not close the USB2 switch again (as on the Pixel Fold; husky's replug is untested) | | `vendor/systemd/logind.conf.d/10-omamobile-power-key.conf` | `/usr/lib/systemd/logind.conf.d` | A short power press does not power the phone off. Same drop-in as the Pixel 7 Pro. On husky the forced reset is Power + Volume Up held 15-30 s ([BRINGUP-M1](../../device/husky/BRINGUP-M1.md) test 23) | | `vendor/NetworkManager/conf.d/10-omamobile-usb.conf` | `/usr/lib/NetworkManager/conf.d` | Keeps NetworkManager off that link | +| `bin/omamobile-husky-display-start` + `vendor/systemd/system/omamobile-husky-display.service` + `display-manager.service.d/10-omamobile-husky.conf` | `/usr/bin`, `/usr/lib/systemd/system` | Loads gs-decon (kernel display PR) before the display manager, hang-safe: a synced marker that a start which never returns leaves behind keeps it off on the next boot, until `--retry`. First it allows the panel's DSI commands (`gs_dsim_cmd.allow_tx=1`, for brightness and 120 Hz), but only when the bootloader names the `google-hk3` panel on the command line, as the Pixel 9a's graphics start does for its panel. Then it sends the brightness systemd restored at boot again, which the panel could only take once `allow_tx` is on. On a kernel without the display PR (derekross/linux-omarchy-mobile#160) the DTB has no DECON0, so the unit is skipped by its condition and the screen stays on simple-framebuffer. With another panel name, `allow_tx` stays off and gs-decon runs read-only at 60 Hz | +| `vendor/modprobe.d/omamobile-husky-display.conf` | `/usr/lib/modprobe.d` | Blacklists gs_decon's autoload, so the display start loads it after `allow_tx`: gs-decon decides on 120 Hz at probe. Sets `screen_off=2`, as cheetah and tegu do: on DPMS off DECON stops its frames and the panel goes to sleep, and DPMS on wakes it | | `vendor/modprobe.d/omamobile-husky-clk-acpm.conf` | `/usr/lib/modprobe.d` | Lets the GPU's ACPM clock move up to 890 MHz, stock's top (`zuma_gpu_max_khz`, kernel #157). The GPU thermal zone throttles it from 85 C. Without it the GPU stays at the bootloader's 150 MHz | | `etc/omamobile-mirrorlist` | `/etc/pacman.d/omamobile-mirrorlist` | Where pacman finds the `[omamobile]` repository. Same file as the Pixel 7 Pro package | | `omamobile-device-husky.install` | pacman hook | Adds `[omamobile]` to `pacman.conf` before `[omarchy]`, once. Same script as the Pixel 7 Pro package | diff --git a/packages/omamobile-device-husky/bin/omamobile-husky-display-start b/packages/omamobile-device-husky/bin/omamobile-husky-display-start new file mode 100755 index 000000000..59b49d3ae --- /dev/null +++ b/packages/omamobile-device-husky/bin/omamobile-husky-display-start @@ -0,0 +1,123 @@ +#!/bin/bash +# SPDX-License-Identifier: MIT +# Bring up the Pixel 8 Pro's display driver at boot, hang-safe. gs_decon is +# blacklisted for autoload (modprobe.d/omamobile-husky-display.conf), so +# this script is the only thing that loads it, after a marker has been +# written and synced. A load or bind that returns but fails is logged and +# the display stays on simple-framebuffer. Only a load that never comes back +# keeps the marker: the next boot finds it, leaves gs_decon alone and says +# so; after reading the previous boot's log, run +# "omamobile-husky-display-start --retry". +# +# The panel's DSI commands (gs_dsim_cmd.allow_tx, for brightness and +# 120 Hz) are allowed only when the bootloader names the google-hk3 panel on +# the command line (exynos_drm.panel_name=google-hk3, with the panel's id +# appended by the bootloader), and before gs_decon loads, since gs-decon +# decides on 120 Hz at probe. As omamobile-tegu-graphics-start does for the +# Pixel 9a's panel. +# omamobile-husky-display-start [--retry] +# OMAMOBILE_HUSKY_ROOT: a scratch root for the package tests (fake /sys, /proc). +set -uo pipefail + +root=${OMAMOBILE_HUSKY_ROOT:-} +if [[ -n $root ]]; then + [[ $root == /* && $root != / && -d $root ]] || exit 2 +fi +state=$root/var/lib/omamobile +marker=$state/husky-display-started +cmdline=$root/proc/cmdline +decon=$root/sys/bus/platform/devices/19470000.display-controller +allow_tx=$root/sys/module/gs_dsim_cmd/parameters/allow_tx + +log() { echo "omamobile-husky-display: $*"; } +# systemd-backlight restores the saved brightness in sysinit, before this +# start allows the panel's commands: the HK3 driver keeps that level and +# sends it with the next write. Write it again now that the panel takes +# commands. (Ordering systemd-backlight after this start instead would put +# the start before sysinit.target, where a hung load would block the boot.) +restore_brightness() { + local bl level + for bl in "$root"/sys/class/backlight/*; do + [[ -e $bl/brightness ]] || continue + level=$(cat "$bl/brightness" 2>/dev/null) || continue + echo "$level" > "$bl/brightness" 2>/dev/null \ + && log "brightness of ${bl##*/}: level $level sent" + done +} +loaded() { [[ -d $root/sys/module/$1 ]]; } +# Wait for a device to bind to a driver: device dir, driver name, quarter seconds. +bound() { + local i + for ((i = 0; i < $3; i++)); do + [[ $(readlink -f "$1/driver" 2>/dev/null) == */$2 ]] && return 0 + sleep 0.25 + done + return 1 +} +# The panel the bootloader named on the kernel command line, or nothing. +panel_name() { + local word + for word in $(cat "$cmdline" 2>/dev/null); do + [[ $word == exynos_drm.panel_name=* ]] && { echo "${word#*=}"; return 0; } + done + echo "" +} + +case ${1:-} in + '') ;; + --retry) rm -f "$marker" ;; + *) log "usage: omamobile-husky-display-start [--retry]"; exit 2 ;; +esac + +if [[ -e $marker ]]; then + log "the last start ($(cat "$marker" 2>/dev/null)) never finished; the display stays on simple-framebuffer this boot." + log "after checking the previous boot's log, retry with: omamobile-husky-display-start --retry" + exit 0 +fi +if [[ ! -e $decon ]]; then + log "no display controller in this DTB; nothing to do" + exit 0 +fi +# Once per boot: a loaded driver is never unloaded or retried. +if [[ ${1:-} != --retry ]] && loaded gs_decon; then + log "already started this boot" + exit 0 +fi + +mkdir -p "$state" +printf '%s display\n' "$(date -Is)" > "$marker" +sync -f "$marker" 2>/dev/null || sync + +# gs_dsim_cmd is not guarded: it autoloads from its node ahead of this start +# and sends nothing until allow_tx is on. Loading it here (a no-op when it +# already is) makes the parameter file exist before the write. +modprobe gs_dsim_cmd 2>/dev/null || true +panel=$(panel_name) +# the bootloader appends the panel's id (google-hk3.20800a on the first phone) +if [[ $panel == google-hk3 || $panel == google-hk3.* ]]; then + if echo 1 > "$allow_tx" 2>/dev/null; then + log "panel $panel: DSI commands allowed (gs_dsim_cmd.allow_tx=1)" + restore_brightness + else + log "panel $panel: could not write $allow_tx; the display stays read-only at 60 Hz" + fi +else + log "panel ${panel:-unnamed}: DSI commands stay off; the display stays read-only at 60 Hz" +fi + +status=0 +# stage=2 is the full driver (the lower stages are bring-up probes) +if ! modprobe gs_decon stage=2 fbdev=0; then + log "gs_decon failed (see dmesg); the display stays on simple-framebuffer" + status=1 +elif ! bound "$decon" gs-decon 60; then + log "the display controller did not bind to gs-decon (see dmesg)" + status=1 +else + log "up: display" +fi + +# The load returned, so the marker is clear; --retry tries it again. +rm -f "$marker" +sync -f "$state" 2>/dev/null || sync +exit $status diff --git a/packages/omamobile-device-husky/install b/packages/omamobile-device-husky/install index 9095179a4..c07b7aba0 100755 --- a/packages/omamobile-device-husky/install +++ b/packages/omamobile-device-husky/install @@ -19,6 +19,17 @@ install -Dm644 vendor/NetworkManager/conf.d/10-omamobile-usb.conf \ "$destination/usr/lib/NetworkManager/conf.d/10-omamobile-usb.conf" install -Dm644 vendor/modprobe.d/omamobile-husky-clk-acpm.conf \ "$destination/usr/lib/modprobe.d/omamobile-husky-clk-acpm.conf" +install -Dm644 vendor/modprobe.d/omamobile-husky-display.conf \ + "$destination/usr/lib/modprobe.d/omamobile-husky-display.conf" +install -Dm755 bin/omamobile-husky-display-start \ + "$destination/usr/bin/omamobile-husky-display-start" +install -Dm644 vendor/systemd/system/omamobile-husky-display.service \ + "$destination/usr/lib/systemd/system/omamobile-husky-display.service" +install -Dm644 vendor/systemd/system/display-manager.service.d/10-omamobile-husky.conf \ + "$destination/usr/lib/systemd/system/display-manager.service.d/10-omamobile-husky.conf" +install -d "$destination/usr/lib/systemd/system/multi-user.target.wants" +ln -sfn ../omamobile-husky-display.service \ + "$destination/usr/lib/systemd/system/multi-user.target.wants/omamobile-husky-display.service" install -Dm644 device.conf \ "$destination/usr/share/omamobile/device.conf" install -Dm644 etc/omamobile-mirrorlist \ diff --git a/packages/omamobile-device-husky/test/all b/packages/omamobile-device-husky/test/all index 1532b704c..8f907f5bd 100755 --- a/packages/omamobile-device-husky/test/all +++ b/packages/omamobile-device-husky/test/all @@ -11,6 +11,7 @@ tmp=$(mktemp -d); trap 'rm -rf "$tmp"' EXIT bash -n build || fail "build parses" bash -n install || fail "install parses" +bash -n bin/omamobile-husky-display-start || fail "the display start parses" pass "scripts parse" grep -q '\.\./\.\.' build install && fail "build or install reaches outside the package directory" @@ -59,6 +60,9 @@ for f in usr/bin/reboot-to \ usr/lib/systemd/logind.conf.d/10-omamobile-power-key.conf \ usr/lib/NetworkManager/conf.d/10-omamobile-usb.conf \ usr/lib/modprobe.d/omamobile-husky-clk-acpm.conf \ + usr/lib/modprobe.d/omamobile-husky-display.conf \ + usr/lib/systemd/system/omamobile-husky-display.service \ + usr/lib/systemd/system/display-manager.service.d/10-omamobile-husky.conf \ usr/share/omamobile/device.conf \ usr/share/omamobile/device-husky/version \ usr/share/licenses/omamobile-device-husky/LICENSE \ @@ -80,7 +84,20 @@ grep -q '^HandlePowerKeyLongPress=ignore$' "$power" \ || fail "the long press stays the PMIC reset" grep -qE '^options clk_acpm zuma_gpu_max_khz=[0-9]+$' "$tmp/root/usr/lib/modprobe.d/omamobile-husky-clk-acpm.conf" \ || fail "the GPU DVFS ceiling is set" -grep -qE '^(install|blacklist) ' vendor/modprobe.d/*.conf && fail "modprobe.d only sets options" +grep -qE '^install ' vendor/modprobe.d/*.conf && fail "an install line in modprobe.d would break the display start's modprobe" +grep -qx 'blacklist gs_decon' "$tmp/root/usr/lib/modprobe.d/omamobile-husky-display.conf" \ + || fail "gs_decon autoloads ahead of the display start" +grep -qx 'options gs_decon screen_off=2' "$tmp/root/usr/lib/modprobe.d/omamobile-husky-display.conf" \ + || fail "DPMS off leaves the panel awake, showing black frames" +[[ $(grep -h '^blacklist ' vendor/modprobe.d/*.conf) == 'blacklist gs_decon' ]] \ + || fail "only gs_decon is guarded" +[[ -x $tmp/root/usr/bin/omamobile-husky-display-start ]] || fail "install stages the display start" +[[ $(readlink "$tmp/root/usr/lib/systemd/system/multi-user.target.wants/omamobile-husky-display.service") == ../omamobile-husky-display.service ]] \ + || fail "the display start is not enabled" +grep -qx 'After=omamobile-husky-display.service' "$tmp/root/usr/lib/systemd/system/display-manager.service.d/10-omamobile-husky.conf" \ + || fail "the display manager can start before the display driver" +grep -qx 'ConditionPathExists=/sys/bus/platform/devices/19470000.display-controller' "$tmp/root/usr/lib/systemd/system/omamobile-husky-display.service" \ + || fail "the display start runs (and fails) on a kernel without DECON0" grep -q '^PACKAGE=omamobile-device-husky$' "$tmp/root/usr/share/omamobile/device.conf" \ || fail "the installed descriptor is husky" for absent in usr/bin/omamobile-boot-success usr/bin/omamobile-bootctl \ @@ -89,11 +106,14 @@ for absent in usr/bin/omamobile-boot-success usr/bin/omamobile-bootctl \ usr/bin/omamobile-camera-start; do [[ ! -e $tmp/root/$absent ]] || fail "install includes $absent" done -pass "install stages the udev rule, the USB link, and the mirrorlist, and nothing that marks a slot or starts hardware" +pass "install stages the udev rule, the USB link, the mirrorlist and the display start, and nothing that marks a slot or starts the radio, the charger or a camera" [[ ! -e $tmp/root/usr/lib/systemd/logind.conf.d/10-omamobile-lid.conf ]] \ || fail "husky has no lid: no lid drop-in" pass "no lid drop-in" +test/display-start || fail "test/display-start" +pass "the display start loads gs_decon after allowing DSI commands for google-hk3 only" + # USB is the last gateway: its route outlives an unplug, so ahead of Wi-Fi # it sent IPv4 into a dead cable (seen on raven, 2026-10-28). net=vendor/systemd/network/20-usb-gadget.network diff --git a/packages/omamobile-device-husky/test/display-start b/packages/omamobile-device-husky/test/display-start new file mode 100755 index 000000000..337ae1557 --- /dev/null +++ b/packages/omamobile-device-husky/test/display-start @@ -0,0 +1,101 @@ +#!/bin/bash +# SPDX-License-Identifier: MIT +# omamobile-husky-display-start in a scratch root: the marker goes down and +# is synced before the first driver loads, the panel's DSI commands are +# allowed for google-hk3 only and before gs_decon, a load that returns and +# fails is logged and clears the marker, and a marker from a previous boot +# keeps gs_decon off until --retry. No hardware is touched: modprobe, sync +# and sleep are fakes on PATH. +set -euo pipefail +cd -- "$(dirname -- "${BASH_SOURCE[0]}")/.." +script=$PWD/bin/omamobile-husky-display-start +fail() { printf 'not ok - display-start: %s\n' "$1" >&2; exit 1; } +tmp=$(mktemp -d); trap 'rm -rf "$tmp"' EXIT +export OMAMOBILE_HUSKY_ROOT=$tmp/root +export TEST_LOG=$tmp/calls +export TEST_ROOT=$OMAMOBILE_HUSKY_ROOT +marker=$OMAMOBILE_HUSKY_ROOT/var/lib/omamobile/husky-display-started +export TEST_MARKER=$marker +decon=$OMAMOBILE_HUSKY_ROOT/sys/bus/platform/devices/19470000.display-controller +allow_tx=$OMAMOBILE_HUSKY_ROOT/sys/module/gs_dsim_cmd/parameters/allow_tx +mkdir -p "$tmp/bin" "$decon" "$OMAMOBILE_HUSKY_ROOT/sys/bus/platform/drivers/gs-decon" +export PATH=$tmp/bin:$PATH +# modprobe: the marker must already be on disk; gs_dsim_cmd brings its +# allow_tx parameter (0, the kernel's default); gs_decon "binds" and its line +# records what allow_tx read when it loaded; FAIL_MODULE fails that load. +cat > "$tmp/bin/modprobe" <<'FAKE' +#!/bin/bash +set -euo pipefail +test -s "$TEST_MARKER" +grep -qx synced "$TEST_LOG" +[[ ${FAIL_MODULE:-} != "$1" ]] || { echo "$*" >> "$TEST_LOG"; exit 1; } +case $1 in + gs_dsim_cmd) p=$TEST_ROOT/sys/module/gs_dsim_cmd/parameters; [[ -e $p/allow_tx ]] || { mkdir -p "$p"; echo 0 > "$p/allow_tx"; } ;; + gs_decon) mkdir -p "$TEST_ROOT/sys/module/gs_decon" + ln -sfn "$TEST_ROOT/sys/bus/platform/drivers/gs-decon" "$TEST_ROOT/sys/bus/platform/devices/19470000.display-controller/driver" + set -- "$@" "allow_tx=$(cat "$TEST_ROOT/sys/module/gs_dsim_cmd/parameters/allow_tx" 2>/dev/null || echo none)" ;; +esac +echo "$*" >> "$TEST_LOG" +FAKE +printf '#!/bin/bash\necho synced >> "$TEST_LOG"\n' > "$tmp/bin/sync" +printf '#!/bin/bash\nexit 0\n' > "$tmp/bin/sleep" +chmod +x "$tmp/bin/"* +cmdline() { mkdir -p "$OMAMOBILE_HUSKY_ROOT/proc"; echo "console=null panic=10 ${1:+exynos_drm.panel_name=$1 }bootconfig" > "$OMAMOBILE_HUSKY_ROOT/proc/cmdline"; } +reset() { + : > "$TEST_LOG" + rm -rf "$marker" "$decon/driver" "$OMAMOBILE_HUSKY_ROOT/sys/module" + mkdir -p "$OMAMOBILE_HUSKY_ROOT/sys/class/backlight/19440000.dsi.0" + echo 900 > "$OMAMOBILE_HUSKY_ROOT/sys/class/backlight/19440000.dsi.0/brightness" + cmdline "${1-google-hk3.20800a}" +} + +# The bootloader's form, the name with the panel's id: allowed before gs_decon +reset +out=$("$script") +[[ ! -e $marker ]] || fail "a finished start leaves the marker" +grep -q '^gs_decon stage=2 fbdev=0 allow_tx=1$' "$TEST_LOG" || fail "allow_tx was not 1 before gs_decon loaded: $(cat "$TEST_LOG")" +[[ $(grep -c '^gs_dsim_cmd' "$TEST_LOG") == 1 ]] || fail "gs_dsim_cmd is loaded once, before the write" +[[ $out == *"panel google-hk3.20800a: DSI commands allowed"* && $out == *"up: display"* ]] || fail "summary: $out" +# the level restored at boot is sent again after allow_tx +[[ $out == *"brightness of 19440000.dsi.0: level 900 sent"* ]] || fail "the brightness is not sent again: $out" +[[ $(cat "$OMAMOBILE_HUSKY_ROOT/sys/class/backlight/19440000.dsi.0/brightness") == 900 ]] || fail "the brightness level changed" + +# The bare name: allowed too +reset google-hk3 +"$script" > /dev/null +grep -q '^gs_decon .*allow_tx=1$' "$TEST_LOG" || fail "google-hk3 without an id is not allowed" + +# Another panel, or none: gs_decon still loads, DSI commands stay off +for p in google-tg4c google-hk3x ""; do + reset "$p" + out=$("$script") + grep -q '^gs_decon .*allow_tx=0$' "$TEST_LOG" || fail "allow_tx turned on for panel '${p}': $(cat "$TEST_LOG")" + [[ $out == *"level 900 sent"* ]] && fail "brightness sent with DSI commands off for '${p}'" + [[ $out == *"DSI commands stay off"* ]] || fail "the refusal for '${p}' is not logged: $out" +done + +# A load that returns and fails: logged, exit 1, the marker cleared +reset +if out=$(FAIL_MODULE=gs_decon "$script"); then fail "a failed gs_decon load exits 0"; fi +[[ ! -e $marker ]] || fail "a failed load that returned keeps the marker" +[[ $out == *"gs_decon failed"* ]] || fail "the failure is not logged: $out" + +# A marker from a previous boot (a load that never came back): nothing loads +reset +mkdir -p "$(dirname "$marker")"; echo "2026-10-31T00:00:00+00:00 display" > "$marker" +out=$("$script") +[[ ! -s $TEST_LOG ]] || fail "a stale marker still loaded: $(cat "$TEST_LOG")" +[[ $out == *"never finished"* && -e $marker ]] || fail "the stale marker is not reported and kept: $out" +# --retry clears it and starts +out=$("$script" --retry) +grep -q '^gs_decon .*allow_tx=1$' "$TEST_LOG" || fail "--retry did not start" +[[ ! -e $marker ]] || fail "--retry leaves the marker" + +# Already started this boot: nothing again +out=$("$script") +[[ $out == *"already started"* ]] || fail "a second start reloads: $out" + +# No display controller in the DTB: nothing to do +reset; rm -rf "$decon" +out=$("$script") +[[ $out == *"no display controller"* && ! -s $TEST_LOG ]] || fail "a DTB without DECON0: $out" diff --git a/packages/omamobile-device-husky/vendor/modprobe.d/omamobile-husky-display.conf b/packages/omamobile-device-husky/vendor/modprobe.d/omamobile-husky-display.conf new file mode 100644 index 000000000..f04c12da6 --- /dev/null +++ b/packages/omamobile-device-husky/vendor/modprobe.d/omamobile-husky-display.conf @@ -0,0 +1,10 @@ +# SPDX-License-Identifier: MIT +# Loaded only by omamobile-husky-display-start, after its marker and after +# it has allowed the panel's DSI commands (gs_dsim_cmd.allow_tx) for the +# google-hk3 panel: gs-decon decides on 120 Hz at probe. Blacklisting only +# stops udev from autoloading it ahead of the start; "modprobe gs_decon" +# still works. No "install" line: that would break the start's own modprobe. +blacklist gs_decon +# The panel really off on DPMS, as on cheetah and tegu: DECON stops its +# frames and the HK3 goes to sleep (screen_off=2); the next DPMS on wakes it. +options gs_decon screen_off=2 diff --git a/packages/omamobile-device-husky/vendor/systemd/system/display-manager.service.d/10-omamobile-husky.conf b/packages/omamobile-device-husky/vendor/systemd/system/display-manager.service.d/10-omamobile-husky.conf new file mode 100644 index 000000000..6113d355f --- /dev/null +++ b/packages/omamobile-device-husky/vendor/systemd/system/display-manager.service.d/10-omamobile-husky.conf @@ -0,0 +1,7 @@ +# SPDX-License-Identifier: MIT +# The display manager starts after the hang-safe display start, so the +# session comes up on gs-decon (at 120 Hz) rather than on simple-framebuffer +# that gs-decon would then take away. +[Unit] +Wants=omamobile-husky-display.service +After=omamobile-husky-display.service diff --git a/packages/omamobile-device-husky/vendor/systemd/system/multi-user.target.wants/omamobile-husky-display.service b/packages/omamobile-device-husky/vendor/systemd/system/multi-user.target.wants/omamobile-husky-display.service new file mode 120000 index 000000000..bc1e0774b --- /dev/null +++ b/packages/omamobile-device-husky/vendor/systemd/system/multi-user.target.wants/omamobile-husky-display.service @@ -0,0 +1 @@ +../omamobile-husky-display.service \ No newline at end of file diff --git a/packages/omamobile-device-husky/vendor/systemd/system/omamobile-husky-display.service b/packages/omamobile-device-husky/vendor/systemd/system/omamobile-husky-display.service new file mode 100644 index 000000000..6a7665d44 --- /dev/null +++ b/packages/omamobile-device-husky/vendor/systemd/system/omamobile-husky-display.service @@ -0,0 +1,21 @@ +# SPDX-License-Identifier: MIT +# The display driver at boot, enabled by the vendor multi-user.target.wants +# link. gs_decon is blacklisted for autoload (modprobe.d/ +# omamobile-husky-display.conf), so this hang-safe script is the only thing +# that loads it; if a start hangs, the next boot leaves it off (see the +# script). Runs before the display manager +# (display-manager.service.d/10-omamobile-husky.conf). +[Unit] +Description=Bring up the Pixel 8 Pro display driver (hang-safe) +After=local-fs.target systemd-modules-load.service +Before=display-manager.service +ConditionPathExists=/sys/bus/platform/devices/19470000.display-controller + +[Service] +Type=oneshot +ExecStart=/usr/bin/omamobile-husky-display-start +RemainAfterExit=yes +TimeoutStartSec=60 + +[Install] +WantedBy=multi-user.target diff --git a/packages/omamobile-device-husky/version b/packages/omamobile-device-husky/version index d917d3e26..b1e80bb24 100644 --- a/packages/omamobile-device-husky/version +++ b/packages/omamobile-device-husky/version @@ -1 +1 @@ -0.1.2 +0.1.3