Repository navigation
kernel config, AGENTS, GNSS-PLAN: follow-ups to #227, and the OnePlus 13 notes - #270
Merged
Merged
Conversation
… 13 notes #227 added CONFIG_PCIE_ZUMAPRO=m, a symbol no published or integration kernel has (it belonged to kernel #168's driver, now superseded by #178's shared zuma-family host), so merge_config dropped it silently; remove it. #227 also made sec_acpm built in for the Pixel 9a's USB PHY. On the 7 Pro that registers the S2MPG13's GNSS rails before the regulator core's 30 s cleanup, and turns the G1 blacklist into a no-op. That is harmless (the rails are GNSS-only), but AGENTS and GNSS-PLAN described load timing the shared kernel can no longer give; they now say so. device/dodge/NOTES.md still called kernel #115 "in review"; it is closed and the kernel stays in the contributor's fork, as DEVICES says (#264). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
derekross
added a commit
that referenced
this pull request
Nov 1, 2026
…#276) #270 called the S2MPG13 rails in cheetah's DT "GNSS-only (LDO9S-11S, LDO15S, and LDO12S when enabled)". LDO15S is vdd_udfps, the fingerprint sensor's supply, and LDO12S is vddio_cam, the cameras' I/O supply; both are claimed by their drivers (on the 7 Pro running a kernel built from main, vddio_cam has 7 users and vdd_udfps 1). Say so, note that the fingerprint and camera starts' modprobe sec_acpm is also a no-op now, and date GNSS-PLAN's "only LDO9S-11S are in the DT" to G1. Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
…e OnePlus 13 notes (derekross#270) derekross#227 added CONFIG_PCIE_ZUMAPRO=m, a symbol no published or integration kernel has (it belonged to kernel derekross#168's driver, now superseded by derekross#178's shared zuma-family host), so merge_config dropped it silently; remove it. derekross#227 also made sec_acpm built in for the Pixel 9a's USB PHY. On the 7 Pro that registers the S2MPG13's GNSS rails before the regulator core's 30 s cleanup, and turns the G1 blacklist into a no-op. That is harmless (the rails are GNSS-only), but AGENTS and GNSS-PLAN described load timing the shared kernel can no longer give; they now say so. device/dodge/NOTES.md still called kernel derekross#115 "in review"; it is closed and the kernel stays in the contributor's fork, as DEVICES says (derekross#264). Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
…derekross#276) derekross#270 called the S2MPG13 rails in cheetah's DT "GNSS-only (LDO9S-11S, LDO15S, and LDO12S when enabled)". LDO15S is vdd_udfps, the fingerprint sensor's supply, and LDO12S is vddio_cam, the cameras' I/O supply; both are claimed by their drivers (on the 7 Pro running a kernel built from main, vddio_cam has 7 users and vdd_udfps 1). Say so, note that the fingerprint and camera starts' modprobe sec_acpm is also a no-op now, and date GNSS-PLAN's "only LDO9S-11S are in the DT" to G1. Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d 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.
Follow-ups found in round 33's commit review:
kernel/configs/omamobile.config: dropCONFIG_PCIE_ZUMAPRO=m. No kernel has the symbol (it was kernel Contributor phones: pacman -U fails when [omamobile] is signed with a local key #168's driver, superseded by device/tegu USB-HOST-PLAN: H2b, H4 and H5 ran on 2026-10-30 #178), so merge_config dropped it silently, and its comment was wrong too (device-tegu blacklists the module).sec_acpmis built in. On the 7 Pro the S2MPG13's GNSS rails register before the 30 s unused-rail cleanup, and the G1 blacklist does nothing. That's harmless, but both documents described load timing the shared kernel no longer gives.device/dodge/NOTES.md: kernel omamobile-shell 0.2.34: home widgets see the phone they run on #115 is closed, not in review (matches DEVICES: the OnePlus 13's kernel stays in its fork #264).Docs and one dead config line; nothing changes on a phone.
🤖 Generated with Claude Code
https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d