Repository navigation
device-panther 0.1.1: the GPU, the haptics and suspend-to-idle - #145
Conversation
|
The failing 🤖 Generated with Claude Code |
|
That flaky stage c9 jump test is fixed in #150: it now waits for the watchdog's first reading, as the other jump tests already do. |
|
Thanks, Alejandro. This is a tidy follow-up to #79. The three files are byte-identical to the Pixel 7 Pro's and the package test compares them, so they can't drift. The s2idle drop-in closes the gap I was worried about while the board file has no Two things before I merge:
The red One more thing since you pushed: I merged #140 (a DEVICES.md and panther-notes refresh after #108), and it touches the same panther lines, so this branch now conflicts with main in On order: this one merges first, and #149 after it, rebased. I'll explain the details there. |
The Pixel 7 Pro's GPU always-on and feedbackd udev rules, and its sleep.conf.d drop-in, byte-identical (the package test compares them). mem_sleep reads "s2idle [deep]" on these kernels, and gs201 never wakes from deep, so Suspend has to be s2idle before anyone taps it. tools/extract-vendor-firmware takes -d panther: the same gs201 vendor files under the same names as cheetah, with panther's board and codename, so the CS40L26 gets this phone's own cs40l26.wmfw and cs40l26.bin. NOTES records the GPU and haptics boots (kernel derekross#129 and derekross#130), that power off restarts the phone within the kernel's first tenth of a second (PSCI SYSTEM_OFF, measured with a shutdown hook that logged to userdata), and that USB stays off the bus after a replug until USI13 is enabled for omamobile-usb-rescue. The Pixel 7 row and BRINGUP-M1 say derekross#108 and derekross#109 are merged, and link the new kernel PRs from the GPU and Haptics cells. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…1/H1 kernels The cmp of the GPU and feedbackd rules against cheetah's copies sat outside the guard that the other comparisons use, so test/all failed wherever the package directory travels alone (phone-install-package, build-packages --container-check). Move it inside the guard, with a pass line, and check the staged rules' content outside it, as the sleep drop-in already is. NOTES' 2026-10-28 GPU and haptics entries now name the kernel release each result came from. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
a69b7d1 to
6177949
Compare
|
Thanks for the careful review. Pushed (
One thing I hit on the way that may be worth a look in the tooling: 🤖 Generated with Claude Code |
|
Thanks, Alejandro. All three points are done, and done well.
I'm merging this now. The GPU node (derekross/linux-omarchy-mobile#129) can follow it, since the always-on rule is in the package. One small thing for #149's rebase, and my fault for telling you to take your side everywhere: BRINGUP-M1's status line now says the FT3658 "had no mainline driver". #140 had changed that to say the chip never answered in boots 7 and 8 because of the supplies, which is what the body of that file and TOUCH-PLAN record (boots 6 and 7 had the driver). #149 touches the same lines. When you rebase it, could you put that sentence back, or better, point it at TOUCH-PLAN's result? Thanks also for the |
The matrix and the Wanted list against what has merged since #140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel #129, #130) were closed because they landed unchanged through kernel #134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite #134, #145 and the 2026-10-28 notes. Touch stays WIP: kernel #134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel #133) and the kernel option with the touch notes (#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel #114, feedbackd's rule in device-raven 0.1.27 (#113). Display names its open kernel PR, #116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (#133) records it scanning through its own UART; kernel #98 and #98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, #104); Suspend describes the merged tier 1 auto-sleep (#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open #171, #172, #174-#176. - Wanted: coral's #52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (#55, #56, #58, #59, split out of #17); the OnePlus 13 (dodge) is listed with #111 and kernel #115, both open. The Pixel 9a row and the Pixel 9 family line are left to #165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…st reading (derekross#150) The stage c9 jump test still raised the estimate 0.4 s after starting the watchdog, so on a slow runner the watchdog took the raised value as its baseline and never muted (seen on derekross#145). It now waits for the watchdog's start line, as the other jump tests do.
…ross#145) The Pixel 7 gets three files from the Pixel 7 Pro's package, byte-identical and compared by the package test when cheetah's package is beside it: - sleep.conf.d/10-omamobile.conf: Suspend means s2idle. The phone offers "deep" (mem_sleep reads "s2idle [deep]"), and gs201 never wakes from it. - 20-omamobile-gpu-always-on.rules, for Panthor on the Mali-G710 (derekross/linux-omarchy-mobile#129). - 72-omamobile-feedbackd.rules, for the CS40L26 haptics (derekross/linux-omarchy-mobile#130). The udev rules match nothing until a kernel has those nodes. A lone copy of the package (phone-install-package, build-packages --container-check) checks the rules' content instead of comparing them. tools/extract-vendor-firmware -d panther extracts the same gs201 files as cheetah under panther's board name, with the same format checks; cheetah's map is unchanged. device/panther/NOTES.md records the GPU (G1) and haptics (H1) boots with their kernel releases, power off restarting the phone (PSCI SYSTEM_OFF), and USB not coming back after a replug. DEVICES.md and BRINGUP-M1 follow. Tested on the Pixel 7 with 0.1.1 installed through phone-install-package: tools/phone-smoke all ok on 7.3.0-rc6-omamobile-push1-g9ec3a2e38705.
The matrix and the Wanted list against what has merged since derekross#140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel derekross#129, derekross#130) were closed because they landed unchanged through kernel derekross#134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (derekross#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite derekross#134, derekross#145 and the 2026-10-28 notes. Touch stays WIP: kernel derekross#134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel derekross#133) and the kernel option with the touch notes (derekross#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel derekross#114, feedbackd's rule in device-raven 0.1.27 (derekross#113). Display names its open kernel PR, derekross#116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (derekross#133) records it scanning through its own UART; kernel derekross#98 and derekross#98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, derekross#104); Suspend describes the merged tier 1 auto-sleep (derekross#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open derekross#171, derekross#172, derekross#174-derekross#176. - Wanted: coral's derekross#52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (derekross#55, derekross#56, derekross#58, derekross#59, split out of derekross#17); the OnePlus 13 (dodge) is listed with derekross#111 and kernel derekross#115, both open. The Pixel 9a row and the Pixel 9 family line are left to derekross#165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
omamobile-device-panther0.1.1, plusextract-vendor-firmware -d pantherand the notes from the Pixel 7's GPU and haptics boots. The kernel side is derekross/linux-omarchy-mobile#129 (GPU) and derekross/linux-omarchy-mobile#130 (haptics, on top of #129).Package. Three files from the Pixel 7 Pro's package, byte-identical; the package test compares each with cheetah's:
sleep.conf.d/10-omamobile.conf: Suspend means s2idle, as you asked on device-panther: Pixel 7 first port, and contributor builds with a local key #79 and arm64: dts: exynos: google: Add Pixel 7 (panther) linux-omarchy-mobile#108. On the phone/sys/power/mem_sleepreadss2idle [deep], so without the drop-in, Omarchy's Suspend would pickdeep, which gs201 never wakes from.mem_sleep_default=s2idlein the bootargs comes with the touch-node kernel PR.20-omamobile-gpu-always-on.rules, for Panthor.72-omamobile-feedbackd.rules, forcs40l26_vibra.The two udev rules match nothing until a kernel has the GPU or haptics node, so the package is safe with today's
omamobile.tools/extract-vendor-firmware -d panther. It extracts the same gs201 vendor files under the same names as cheetah, with panther's board and codename substituted, and checks the haptics and media deltas as it does for cheetah. Run on this phone's factory image (CP3A.261005.002.A1), it exits 0 and givescs40l26.wmfwandcs40l26.bin; that is what the haptics test used.Notes (
device/panther/NOTES.md, 2026-10-28):ff-rumbleeffects felt;userdataten times a second, then powered off itself with sysrqo. Nothing was saved after the trigger, so the reset comes within the first tenth of a second ofkernel_power_off(), from PSCI SYSTEM_OFF (syscon-poweroffwas disabled in the test DT). The Pixel 7 Pro hasn't powered off from Linux either (SUSPEND-PLAN P7), so this may be useful there;omamobile-usb-rescueneeds USI13, which the panther board file doesn't enable yet; that's the next kernel step.Matrix. The Pixel 7 row and BRINGUP-M1 now say #108 and #109 are merged:
The rest of #79's follow-ups (Touch "works", the touch drop-ins,
CONFIG_TOUCHSCREEN_FOCALTECH_FT3658=m) come with the touch PR.Checks:
tests/all(194 ok, on main at a6034a5),tools/pr-check upstream/main, and the panther package's test, both from the repository and from a lone copy of the package directory.Phone evidence (CONTRIBUTING §6.5). The phone runs this package, 0.1.1, built and installed on it with
tools/phone-install-package(itscheck()rantest/allon the lone package directory and passed), with the hand-installed rule copies removed. The kernel is derekross/linux-omarchy-mobile#134 atace1ba57fmerged with derekross/linux-omarchy-mobile#133 atfdc4f4403, the build T6 tested (g8d46192a301e), plus one local commit on top that enables the MAX77759's I2C bus (USI13) foromamobile-usb-rescue, the next kernel PR.phone-smoke: panther
Kernel
7.3.0-rc6-omamobile-push1-g9ec3a2e38705, tools at6177949, 2026-10-29T20:57Z.Packages: hyprland 0.56.2-5.1, libcamera 0.7.2-4.21, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamobile-apps 0.2.0-1, omamobile-device-panther 0.1.1-1, omamobile-firstboot 0.1.2-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.12-1, omamobile-owl-widgets 0.1.1-1, omamobile-shell 0.2.28-1, omarchy 4.0.6-1, quickshell 0.3.2.r7.g2b4501a-1
🤖 Generated with Claude Code