Repository navigation
device-panther: load the camera drivers after boot, as cheetah - #430
Closed
angelrenefm wants to merge 1 commit into
Closed
angelrenefm wants to merge 1 commit into
angelrenefm wants to merge 1 commit into
Conversation
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.
Owner
|
Thanks, this mirrors the 7 Pro's camera start closely, and the test checks the two differences that matter (panther's CSIS and no telephoto focus driver) and that every driver stays blacklisted. Shipping the blacklist before the camera nodes exist is the right order. I'll merge it and set the version then. When you propose the camera device tree, please mention in it which CSIS each sensor uses, so the |
derekross
added a commit
that referenced
this pull request
Nov 5, 2026
#443, from #428 and #430) Two device-panther changes from angelrenefm (#428, #430), carried together because they conflict in the README and neither bumped the version (main was at 0.1.8): - The DMA heap rule, cheetah's file unchanged: libcamera's software ISP allocates from /dev/dma_heap, which was root-only on the Pixel 7, so the camera app got raw frames it couldn't show. - The camera start, cheetah's with two changes: it checks panther's CSIS (1a450000) and doesn't load sem1215, the telephoto's focus controller. The drivers never autoload; the timer loads them 40 s into the boot behind a hang marker, and on a DTB without the camera receiver the service's condition skips it. Both stay inert until the camera device tree is proposed. Co-authored-by: Ángel René <17342133+angelrenefm@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
derekross#443, from derekross#428 and derekross#430) Two device-panther changes from angelrenefm (derekross#428, derekross#430), carried together because they conflict in the README and neither bumped the version (main was at 0.1.8): - The DMA heap rule, cheetah's file unchanged: libcamera's software ISP allocates from /dev/dma_heap, which was root-only on the Pixel 7, so the camera app got raw frames it couldn't show. - The camera start, cheetah's with two changes: it checks panther's CSIS (1a450000) and doesn't load sem1215, the telephoto's focus controller. The drivers never autoload; the timer loads them 40 s into the boot behind a hang marker, and on a DTB without the camera receiver the service's condition skips it. Both stay inert until the camera device tree is proposed. Co-authored-by: Ángel René <17342133+angelrenefm@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Pixel 7 had no
omamobile-camera-start, so its cameras only came up when the drivers were loaded by hand. This ships the Pixel 7 Pro's blacklist (omamobile-camera.conf, 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 waits for is1a450000.csis(cheetah's is1a460000), and it doesn't loadsem1215, the telephoto's focus controller (no telephoto). On a DTB without the camera receiver enabled, as onomamobiletoday, the service's condition skips it and nothing loads.Measured on a second Pixel 7 with the camera nodes from kernel commits not yet proposed and the camera overlays, the same 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, near and far.
Not checked: this package build installed on the phone.
Checks:
test/all(files staged, the timer's wants link, panther's CSIS in the script and the unit, nosem1215, every driver it loads except the PMIC core blacklisted, the list identical to cheetah's; with cheetah's CSIS address it fails) andtools/pr-check origin/mainpass.tools/phone-smoke (the same phone, 2026-11-04T18:47Z)
phone-smoke: panther
Kernel
7.3.0-rc6-omamobile-push1-g44048a9aa795, tools at3435ed4, 2026-11-04T18:47Z.Packages: hyprland 0.57.0-3.1, libcamera 0.7.2-4.22, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamobile-apps 0.2.0-1, omamobile-audio 0.5.13-1, omamobile-device-panther 0.1.5-1, omamobile-firstboot 0.1.3-1, omamobile-gnss 0.2.7-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.28-1, omamobile-owl-widgets 0.1.1-1, omamobile-sensors 0.2.1-1, omamobile-shell 0.2.79-1, omarchy 4.0.6-1, quickshell 0.3.2.r7.g2b4501a-1
I used AI help (Claude) to work on this.