From 17e928c4199435f0b31badf0e83291abccc3d370 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81ngel=20Ren=C3=A9?= <17342133+angelrenefm@users.noreply.github.com> Date: Wed, 4 Nov 2026 00:03:08 +0100 Subject: [PATCH 1/3] device-panther: open the DMA heaps to the video group, as cheetah libcamera's software ISP allocates its buffers from /dev/dma_heap. Without cheetah's rule the heaps are root-only on the Pixel 7, so the simple pipeline logs "Could not open any dma-buf provider", disables software debayering, and the camera app gets raw BA10 frames it can't show. The rule is cheetah's file, unchanged; test/all checks that it stays so and that install stages it. Tested on a Pixel 7 with the camera nodes from kernel commits not yet proposed and the camera overlays: with the rule copied by hand, omacam streams the main camera at 2008x1136. This package build itself has not been installed on the phone. I used AI help (Claude) to work on this. (cherry picked from commit e39c8d368a4afff0d84037d965c4f2c8bb722dea) --- packages/omamobile-device-panther/README.md | 1 + packages/omamobile-device-panther/install | 3 ++- packages/omamobile-device-panther/test/all | 5 +++-- .../vendor/udev/rules.d/70-omamobile-dma-heap.rules | 8 ++++++++ 4 files changed, 14 insertions(+), 3 deletions(-) create mode 100644 packages/omamobile-device-panther/vendor/udev/rules.d/70-omamobile-dma-heap.rules diff --git a/packages/omamobile-device-panther/README.md b/packages/omamobile-device-panther/README.md index e375aeaa0..9b632c2b2 100644 --- a/packages/omamobile-device-panther/README.md +++ b/packages/omamobile-device-panther/README.md @@ -7,6 +7,7 @@ Omarchy Mobile's first userspace package for the Google Pixel 7 (codename panthe | `vendor/udev/rules.d/10-omamobile-storage.rules` | `/usr/lib/udev/rules.d` | Hides `sda` and every Android partition except `userdata` from desktop tools. Same rule as the Pixel 7 Pro. The initramfs stops its guard loop before `switch_root`; the kernel's read-only flags are what remain | | `vendor/udev/rules.d/20-omamobile-gpu-always-on.rules` | `/usr/lib/udev/rules.d` | Keeps the Mali-G710 powered while Panthor drives it: powering its domain back up needs a secure call our kernel doesn't make yet. Same rule as the Pixel 7 Pro | | `vendor/udev/rules.d/72-omamobile-feedbackd.rules` | `/usr/lib/udev/rules.d` | Lets feedbackd drive the CS40L26 haptics (`cs40l26_vibra`). Same rule as the Pixel 7 Pro; the driver needs the phone's own `cs40l26.wmfw` (`tools/extract-vendor-firmware -d panther`) | +| `vendor/udev/rules.d/70-omamobile-dma-heap.rules` | `/usr/lib/udev/rules.d` | Lets the video group (and the seat's user) use the general DMA-BUF heaps, which libcamera's software ISP needs in a user session. Same rule as the Pixel 7 Pro | | `vendor/systemd/network/20-usb-gadget.network` | `/usr/lib/systemd/network` | Sets usb0 to 172.16.42.1/24 after handover | | `bin/omamobile-usb-rescue`, `vendor/systemd/system/omamobile-usb-rescue.service` | `/usr/bin`, `/usr/lib/systemd/system` (enabled for `multi-user.target`) | Brings USB back after a replug: the MAX77759 opens its USB2 data switch on unplug, and with no Type-C driver nothing closes it. While VBUS is valid, puts the switch back to 0x09 on the chip's I2C bus (USI13, which the board file enables). Reads two registers and writes that one; stands aside once a Type-C driver owns the chip. Same script and unit as the Pixel 7 Pro; needs `i2c-tools` | | `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. The long press stays the PMIC reset | diff --git a/packages/omamobile-device-panther/install b/packages/omamobile-device-panther/install index e8b009dc2..29ab64509 100755 --- a/packages/omamobile-device-panther/install +++ b/packages/omamobile-device-panther/install @@ -17,7 +17,8 @@ ln -sfn ../omamobile-usb-rescue.service \ "$destination/usr/lib/systemd/system/multi-user.target.wants/omamobile-usb-rescue.service" install -Dm644 vendor/udev/rules.d/10-omamobile-storage.rules \ "$destination/usr/lib/udev/rules.d/10-omamobile-storage.rules" -for rules in 20-omamobile-gpu-always-on.rules 72-omamobile-feedbackd.rules; do +for rules in 20-omamobile-gpu-always-on.rules 72-omamobile-feedbackd.rules \ + 70-omamobile-dma-heap.rules; do install -Dm644 "vendor/udev/rules.d/$rules" "$destination/usr/lib/udev/rules.d/$rules" done install -Dm644 vendor/systemd/network/20-usb-gadget.network \ diff --git a/packages/omamobile-device-panther/test/all b/packages/omamobile-device-panther/test/all index 338880eb3..858540bd7 100755 --- a/packages/omamobile-device-panther/test/all +++ b/packages/omamobile-device-panther/test/all @@ -40,11 +40,11 @@ if [[ -f ../omamobile-device-cheetah/src/reboot-to.c ]]; then ../omamobile-device-cheetah/vendor/systemd/sleep.conf.d/10-omamobile.conf \ || fail "the sleep drop-in drifted from the cheetah package" pass "the sleep drop-in matches the cheetah package" - for rules in 20-omamobile-gpu-always-on.rules 72-omamobile-feedbackd.rules; do + for rules in 20-omamobile-gpu-always-on.rules 72-omamobile-feedbackd.rules 70-omamobile-dma-heap.rules; do cmp -s "vendor/udev/rules.d/$rules" "../omamobile-device-cheetah/vendor/udev/rules.d/$rules" \ || fail "$rules drifted from the cheetah package" done - pass "the GPU and feedbackd rules match the cheetah package" + pass "the GPU, feedbackd and DMA heap rules match the cheetah package" cmp -s omamobile-device-panther.install \ ../omamobile-device-cheetah/omamobile-device-cheetah.install \ || fail "the pacman install script drifted from the cheetah package" @@ -77,6 +77,7 @@ for f in usr/bin/reboot-to \ usr/lib/udev/rules.d/10-omamobile-storage.rules \ usr/lib/udev/rules.d/20-omamobile-gpu-always-on.rules \ usr/lib/udev/rules.d/72-omamobile-feedbackd.rules \ + usr/lib/udev/rules.d/70-omamobile-dma-heap.rules \ usr/lib/systemd/network/20-usb-gadget.network \ usr/lib/systemd/logind.conf.d/10-omamobile-power-key.conf \ usr/lib/systemd/sleep.conf.d/10-omamobile.conf \ diff --git a/packages/omamobile-device-panther/vendor/udev/rules.d/70-omamobile-dma-heap.rules b/packages/omamobile-device-panther/vendor/udev/rules.d/70-omamobile-dma-heap.rules new file mode 100644 index 000000000..2341cae32 --- /dev/null +++ b/packages/omamobile-device-panther/vendor/udev/rules.d/70-omamobile-dma-heap.rules @@ -0,0 +1,8 @@ +# SPDX-License-Identifier: MIT +# libcamera's software ISP (and so PipeWire's libcamera plugin, which runs in +# the user's WirePlumber) allocates its output buffers from the DMA-BUF heaps. +# They are root-only by default, so without this a user session saw the +# cameras but got no debayered stream ("Could not open any dma-buf provider", +# device/cheetah/CAMERA-PLAN.md CAM5.4). Give the video group and the seat's +# user the general heaps; the camera and display pools stay the kernel's. +SUBSYSTEM=="dma_heap", KERNEL=="system|reserved|default_cma_region", GROUP="video", MODE="0660", TAG+="uaccess" From 5b641bbc6718bb13dd738a408cf6b18622e98de5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81ngel=20Ren=C3=A9?= <17342133+angelrenefm@users.noreply.github.com> Date: Wed, 4 Nov 2026 19:42:56 +0100 Subject: [PATCH 2/3] device-panther: load the camera drivers after boot, as cheetah The Pixel 7 had no omamobile-camera-start, so its cameras only came up when their drivers were loaded by hand. Ship the Pixel 7 Pro's blacklist (unchanged), script, service and timer: the drivers never autoload, and 40 s into the boot the script loads the camera PMIC drivers, the sensors and lenses, the DC-PHY and the CSIS behind a hang marker. Two changes for panther: the CSIS it checks for is 1a450000 (cheetah's is 1a460000), and it does not load sem1215, the telephoto's focus controller (no telephoto here). On a DTB without the camera receiver enabled, as on omamobile today, the service's condition skips it and nothing loads. test/all: the files are staged, the timer is enabled by a wants link, the script and unit use panther's CSIS, every driver it loads but the PMIC core is blacklisted, the list matches cheetah's. On a Pixel 7 with the camera nodes from kernel commits not yet proposed and the camera overlays, with these files copied by hand and the timer enabled: the script ran in 0.3 s and left three media graphs (imx386; s5kgn1 with ak7375; s5k3j1), and autofocus worked in omacam. This package build has not been installed on the phone. I used AI help (Claude) to work on this. (cherry picked from commit 829dbbd66cf73fc5c695f4f43db1400294b3b42a) --- packages/omamobile-device-panther/README.md | 5 +- .../bin/omamobile-camera-start | 52 +++++++++++++++++++ packages/omamobile-device-panther/install | 14 ++++- packages/omamobile-device-panther/test/all | 27 +++++++++- .../vendor/modprobe.d/omamobile-camera.conf | 29 +++++++++++ .../systemd/system/omamobile-camera.service | 12 +++++ .../systemd/system/omamobile-camera.timer | 13 +++++ 7 files changed, 147 insertions(+), 5 deletions(-) create mode 100755 packages/omamobile-device-panther/bin/omamobile-camera-start create mode 100644 packages/omamobile-device-panther/vendor/modprobe.d/omamobile-camera.conf create mode 100644 packages/omamobile-device-panther/vendor/systemd/system/omamobile-camera.service create mode 100644 packages/omamobile-device-panther/vendor/systemd/system/omamobile-camera.timer diff --git a/packages/omamobile-device-panther/README.md b/packages/omamobile-device-panther/README.md index 9b632c2b2..3fdeaa71e 100644 --- a/packages/omamobile-device-panther/README.md +++ b/packages/omamobile-device-panther/README.md @@ -1,6 +1,6 @@ # omamobile-device-panther -Omarchy Mobile's first userspace package for the Google Pixel 7 (codename panther, Tensor G2 / gs201). It hides the Android partitions from desktop tools, holds the USB address and brings USB back after a replug, and gives pacman the same `[omamobile]` repository as the Pixel 7 Pro. It does not drive the radio, the charger, or a camera, and it does not mark a boot slot successful. +Omarchy Mobile's first userspace package for the Google Pixel 7 (codename panther, Tensor G2 / gs201). It hides the Android partitions from desktop tools, holds the USB address and brings USB back after a replug, and gives pacman the same `[omamobile]` repository as the Pixel 7 Pro. It loads the camera drivers after the boot has settled. It does not drive the radio or the charger, and it does not mark a boot slot successful. | Path | Installs to | What it does | | --- | --- | --- | @@ -8,6 +8,7 @@ Omarchy Mobile's first userspace package for the Google Pixel 7 (codename panthe | `vendor/udev/rules.d/20-omamobile-gpu-always-on.rules` | `/usr/lib/udev/rules.d` | Keeps the Mali-G710 powered while Panthor drives it: powering its domain back up needs a secure call our kernel doesn't make yet. Same rule as the Pixel 7 Pro | | `vendor/udev/rules.d/72-omamobile-feedbackd.rules` | `/usr/lib/udev/rules.d` | Lets feedbackd drive the CS40L26 haptics (`cs40l26_vibra`). Same rule as the Pixel 7 Pro; the driver needs the phone's own `cs40l26.wmfw` (`tools/extract-vendor-firmware -d panther`) | | `vendor/udev/rules.d/70-omamobile-dma-heap.rules` | `/usr/lib/udev/rules.d` | Lets the video group (and the seat's user) use the general DMA-BUF heaps, which libcamera's software ISP needs in a user session. Same rule as the Pixel 7 Pro | +| `bin/omamobile-camera-start` + `vendor/systemd/system/omamobile-camera.{service,timer}` + `vendor/modprobe.d/omamobile-camera.conf` | `/usr/bin`, `/usr/lib/systemd/system` (the timer enabled by a vendor wants link), `/usr/lib/modprobe.d` | Loads the camera drivers 40 s into the boot (PMIC supplies, the three sensors and the main camera's lens, the DC-PHY and CSIS), skipping them on the next boot if a load never finished, and only when the DTB enables the camera receiver (`1a450000.csis`). The modules are blacklisted for autoload so only this guard (or a runbook) loads them. The Pixel 7 Pro's script, unit and list, with panther's CSIS and without the telephoto's `sem1215` | | `vendor/systemd/network/20-usb-gadget.network` | `/usr/lib/systemd/network` | Sets usb0 to 172.16.42.1/24 after handover | | `bin/omamobile-usb-rescue`, `vendor/systemd/system/omamobile-usb-rescue.service` | `/usr/bin`, `/usr/lib/systemd/system` (enabled for `multi-user.target`) | Brings USB back after a replug: the MAX77759 opens its USB2 data switch on unplug, and with no Type-C driver nothing closes it. While VBUS is valid, puts the switch back to 0x09 on the chip's I2C bus (USI13, which the board file enables). Reads two registers and writes that one; stands aside once a Type-C driver owns the chip. Same script and unit as the Pixel 7 Pro; needs `i2c-tools` | | `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. The long press stays the PMIC reset | @@ -21,4 +22,4 @@ Omarchy Mobile's first userspace package for the Google Pixel 7 (codename panthe `./build [DIR]` compiles `reboot-to` from this directory, `./install DESTDIR [DIR]` stages the files, and `test/all` checks the copies when it is run from the repository. -Not in this package: the boot-success marker, Wi-Fi, the charger, cameras, and the slot-B image hook. Those stay out until each one has its own runbook. +Not in this package: the boot-success marker, Wi-Fi, the charger, and the slot-B image hook. Those stay out until each one has its own runbook. diff --git a/packages/omamobile-device-panther/bin/omamobile-camera-start b/packages/omamobile-device-panther/bin/omamobile-camera-start new file mode 100755 index 000000000..87c32be23 --- /dev/null +++ b/packages/omamobile-device-panther/bin/omamobile-camera-start @@ -0,0 +1,52 @@ +#!/bin/bash +# SPDX-License-Identifier: MIT +# Load the camera drivers once the system is up (device/cheetah/CAMERA-PLAN.md +# CAM5.4), hang-safe like omamobile-aoc-start. +# +# The modules stay blacklisted for autoload (modprobe.d/omamobile-camera.conf): +# this script is what loads them, from omamobile-camera.timer some time after +# boot, so nothing camera-related runs while the boot is still settling. Order: +# 1. the PMIC drivers behind the camera supplies (sec_acpm for LDO12S, +# gpio_s2mpg13 for the fixed supplies' enables, slg51002_regulator for +# the camera PMIC); +# 2. the sensors and lenses (each sensor powers up for its chip ID and off +# again; the lenses power up only while their subdev is open); +# 3. the DC-PHY and the CSIS driver, which registers the media graphs +# libcamera (and PipeWire's libcamera plugin) find. +# Nothing streams until an application asks. A marker is written and synced +# first and removed at the end: if a boot hangs here, the next boot leaves +# the cameras off; "omamobile-camera-start --retry" tries again. +set -uo pipefail + +marker=/var/lib/omamobile/camera-start-started +log() { echo "omamobile-camera: $*"; } + +[[ ${1:-} == --retry ]] && rm -f "$marker" +if [[ -e $marker ]]; then + log "the last start ($(cat "$marker" 2>/dev/null)) never finished; the cameras stay off this boot." + log "after checking the previous boot's log, retry with: omamobile-camera-start --retry" + exit 0 +fi +if [[ ! -e /sys/bus/platform/devices/1a450000.csis ]]; then + log "the camera receiver is not enabled in this DTB; nothing to do" + exit 0 +fi + +mkdir -p "${marker%/*}" +date -Is > "$marker" && sync -f "$marker" + +load() { + local m + for m; do + modprobe "$m" || log "modprobe $m failed" + done +} +load sec_acpm gpio_s2mpg13 slg51002_regulator +udevadm settle -t 10 +load imx386 s5kgn1 ak7375 phy_gs201_mipi_dcphy_rx gs201_csis +udevadm settle -t 10 + +rm -f "$marker" +sync -f "${marker%/*}" +n=$(ls -d /sys/bus/media/devices/media* 2>/dev/null | wc -l) +log "camera drivers loaded; $n media devices" diff --git a/packages/omamobile-device-panther/install b/packages/omamobile-device-panther/install index 29ab64509..58fb25dd4 100755 --- a/packages/omamobile-device-panther/install +++ b/packages/omamobile-device-panther/install @@ -1,7 +1,9 @@ #!/bin/bash # SPDX-License-Identifier: MIT # Stage omamobile-device-panther into DESTDIR. Nothing is enabled that would -# mark a slot successful or start the radio, the charger, or a camera. +# mark a slot successful or start the radio or the charger. The camera +# drivers load only from omamobile-camera.timer, 40 s into the boot, behind +# a hang marker, and only on a DTB with the camera receiver enabled. # ./install DESTDIR [BUILDDIR] set -euo pipefail cd -- "$(dirname -- "${BASH_SOURCE[0]}")" @@ -29,6 +31,16 @@ install -Dm644 vendor/systemd/sleep.conf.d/10-omamobile.conf \ "$destination/usr/lib/systemd/sleep.conf.d/10-omamobile.conf" install -Dm644 vendor/modprobe.d/omamobile-display.conf \ "$destination/usr/lib/modprobe.d/omamobile-display.conf" +# The camera drivers never autoload; omamobile-camera-start loads them. +install -Dm644 vendor/modprobe.d/omamobile-camera.conf \ + "$destination/usr/lib/modprobe.d/omamobile-camera.conf" +install -Dm755 bin/omamobile-camera-start "$destination/usr/bin/omamobile-camera-start" +for unit in omamobile-camera.service omamobile-camera.timer; do + install -Dm644 "vendor/systemd/system/$unit" "$destination/usr/lib/systemd/system/$unit" +done +install -d "$destination/usr/lib/systemd/system/timers.target.wants" +ln -sfn ../omamobile-camera.timer \ + "$destination/usr/lib/systemd/system/timers.target.wants/omamobile-camera.timer" install -Dm644 vendor/NetworkManager/conf.d/10-omamobile-usb.conf \ "$destination/usr/lib/NetworkManager/conf.d/10-omamobile-usb.conf" install -Dm644 device.conf \ diff --git a/packages/omamobile-device-panther/test/all b/packages/omamobile-device-panther/test/all index 858540bd7..8ccb320dd 100755 --- a/packages/omamobile-device-panther/test/all +++ b/packages/omamobile-device-panther/test/all @@ -82,6 +82,9 @@ for f in usr/bin/reboot-to \ usr/lib/systemd/logind.conf.d/10-omamobile-power-key.conf \ usr/lib/systemd/sleep.conf.d/10-omamobile.conf \ usr/lib/modprobe.d/omamobile-display.conf \ + usr/lib/modprobe.d/omamobile-camera.conf \ + usr/lib/systemd/system/omamobile-camera.service \ + usr/lib/systemd/system/omamobile-camera.timer \ usr/lib/NetworkManager/conf.d/10-omamobile-usb.conf \ usr/share/omamobile/device.conf \ usr/share/omamobile/device-panther/version \ @@ -122,11 +125,31 @@ grep -q '^PACKAGE=omamobile-device-panther$' "$tmp/root/usr/share/omamobile/devi for absent in usr/bin/omamobile-boot-success usr/bin/omamobile-bootctl \ usr/lib/systemd/system/omamobile-boot-success.service \ usr/bin/omamobile-wifi-start usr/bin/omamobile-charge-guard \ - usr/bin/omamobile-camera-start \ usr/lib/systemd/logind.conf.d/10-omamobile-lid.conf; do [[ ! -e $tmp/root/$absent ]] || fail "install includes $absent" done -pass "install stages the udev rules, the USB link and its rescue, and the mirrorlist, and nothing that marks a slot or starts hardware" +pass "install stages the udev rules, the USB link and its rescue, and the mirrorlist, and nothing that marks a slot or starts the radio or the charger" +# The cameras: drivers blacklisted, loaded only by omamobile-camera-start +# from the timer, on panther's CSIS (1a450000; cheetah's is 1a460000). +cam=$tmp/root/usr/bin/omamobile-camera-start +[[ -x $cam ]] || fail "omamobile-camera-start is executable" +[[ $(readlink "$tmp/root/usr/lib/systemd/system/timers.target.wants/omamobile-camera.timer") == ../omamobile-camera.timer ]] \ + || fail "the camera timer is enabled by a vendor wants link" +grep -qx 'OnBootSec=40s' "$tmp/root/usr/lib/systemd/system/omamobile-camera.timer" || fail "the cameras load 40 s into the boot" +grep -qx 'ConditionPathExists=/sys/bus/platform/devices/1a450000.csis' "$tmp/root/usr/lib/systemd/system/omamobile-camera.service" \ + || fail "the camera service waits for panther's CSIS" +grep -q '/sys/bus/platform/devices/1a450000.csis' "$cam" || fail "the script checks panther's CSIS" +grep -q '1a460000' "$cam" "$tmp/root/usr/lib/systemd/system/omamobile-camera.service" && fail "cheetah's CSIS address left in" +grep -q 'sem1215' "$cam" && fail "panther has no telephoto: sem1215 is not loaded" +for m in $(sed -n 's/^load //p' "$cam"); do + [[ $m == sec_acpm ]] && continue # the PMIC core, not in cheetah's list either + grep -qx "blacklist $m" "$tmp/root/usr/lib/modprobe.d/omamobile-camera.conf" \ + || fail "the camera driver $m must not autoload" +done +grep -q 'camera-start-started' "$cam" && grep -q 'sync -f "$marker"' "$cam" || fail "omamobile-camera-start writes and syncs a hang marker" +cmp -s vendor/modprobe.d/omamobile-camera.conf ../omamobile-device-cheetah/vendor/modprobe.d/omamobile-camera.conf 2>/dev/null \ + || [[ ! -d ../omamobile-device-cheetah ]] || fail "the camera blacklist drifted from the cheetah package" +pass "the camera drivers never autoload; omamobile-camera-start loads them from a timer, on panther's CSIS" # 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-panther/vendor/modprobe.d/omamobile-camera.conf b/packages/omamobile-device-panther/vendor/modprobe.d/omamobile-camera.conf new file mode 100644 index 000000000..8ce6984e2 --- /dev/null +++ b/packages/omamobile-device-panther/vendor/modprobe.d/omamobile-camera.conf @@ -0,0 +1,29 @@ +# SPDX-License-Identifier: MIT +# The camera drivers don't autoload: omamobile-camera-start (from +# omamobile-camera.timer, 40 s into the boot) loads them in order, and the +# bring-up runbooks (device/cheetah/CAMERA-PLAN.md) load them by hand. +# Explicit modprobe still works. +# +# S2MPG13 GPIOs: binding it lets the fixed camera supplies probe, which +# drives their enable pins low. +blacklist gpio_s2mpg13 +# SLG51002 camera PMIC: raises its chip select at probe. +blacklist slg51002_regulator +# Camera module power test driver (debugfs power-up and ID reads). +blacklist gs201_cam_power +# Read-only CSIS power and register probe (no DT node; never autoloads). +blacklist gs201_cam_probe +# Capture path (CAM3b/CAM4): the IMX386 sensor (powers the module at probe +# to read its ID), the DC-PHY receiver and the CSIS link + WDMA driver. +blacklist imx386 +blacklist phy_gs201_mipi_dcphy_rx +blacklist gs201_csis +# Main camera and the focus actuators (CAMERA-PLAN.md CAM-M, CAM5.3): the +# Samsung S5KGN1 sensor (powers the module at probe to read its ID; the +# same driver runs the front S5K3J1 and the telephoto S5KGM5, CAM7/CAM-T) +# and the AK7375-type VCM drivers of the main and ultrawide modules. +blacklist s5kgn1 +blacklist ak7375 +# The telephoto's SEM1215SA focus controller (CAM-T): powers it at probe +# to read the focus calibration, and whenever its subdev is open. +blacklist sem1215 diff --git a/packages/omamobile-device-panther/vendor/systemd/system/omamobile-camera.service b/packages/omamobile-device-panther/vendor/systemd/system/omamobile-camera.service new file mode 100644 index 000000000..9768f9860 --- /dev/null +++ b/packages/omamobile-device-panther/vendor/systemd/system/omamobile-camera.service @@ -0,0 +1,12 @@ +# SPDX-License-Identifier: MIT +# Load the camera drivers (hang-safe script; device/cheetah/CAMERA-PLAN.md +# CAM5.4). Started by omamobile-camera.timer, after the boot has settled. +[Unit] +Description=Load the camera drivers (hang-safe) +After=multi-user.target omamobile-aoc.service +ConditionPathExists=/sys/bus/platform/devices/1a450000.csis + +[Service] +Type=oneshot +ExecStart=/usr/bin/omamobile-camera-start +RemainAfterExit=yes diff --git a/packages/omamobile-device-panther/vendor/systemd/system/omamobile-camera.timer b/packages/omamobile-device-panther/vendor/systemd/system/omamobile-camera.timer new file mode 100644 index 000000000..b72cb6f9f --- /dev/null +++ b/packages/omamobile-device-panther/vendor/systemd/system/omamobile-camera.timer @@ -0,0 +1,13 @@ +# SPDX-License-Identifier: MIT +# The camera drivers load 40 s into the boot: after the regulator core's +# unused-supply clean-up (about 30 s after late init) and once the session is +# up, so a problem with them never holds up the boot. +[Unit] +Description=Load the camera drivers after the boot has settled + +[Timer] +OnBootSec=40s +AccuracySec=1s + +[Install] +WantedBy=timers.target From e36e56f9410d2677e5ecf7d74d1e4ddfb8db678a Mon Sep 17 00:00:00 2001 From: Derek Ross Date: Thu, 5 Nov 2026 16:30:59 -0500 Subject: [PATCH 3/3] omamobile-device-panther 0.1.9: the camera start and the DMA heap rule (#428, #430) angelrenefm's two device-panther changes, carried together because they conflict with each other in the README and neither bumped the version (main is at 0.1.8 since #418). The README keeps both rows. Co-Authored-By: Claude Opus 5.5 --- packages/omamobile-device-panther/version | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/omamobile-device-panther/version b/packages/omamobile-device-panther/version index 699c6c6d4..1a030947e 100644 --- a/packages/omamobile-device-panther/version +++ b/packages/omamobile-device-panther/version @@ -1 +1 @@ -0.1.8 +0.1.9