Repository navigation
device/tegu, omamobile-device-tegu: the Pixel 9a's modem and GNSS from the published kernel's own drivers - #594
Conversation
…em and GNSS from the published kernel's own drivers The board's device tree has only the modem node under the PCIe link, so a 9a built from the tree had no cpif node and the modem start could only use the owner's bring-up modules. device/tegu/overlays/modem-cpif.dtso is the published form of the bring-up overlay (paths, no labels): it hands the modem node to CPIF and adds the cpif and cp-shmem nodes, and the descriptor lists it in DTB_OVERLAYS. The shared config builds the GNSS link driver (CONFIG_EXYNOS_GNSS_IF_SPI=m, linux-omarchy-mobile#185), and the 9a's guards keep gnss_spi and gnssif from autoloading, like CPIF's modules, so only the modem start loads them. MODEM-PLAN records the run on the palmtop: three boots by the boot unit on the in-tree drivers, the confirmed stop, four GNSS sessions, and why the GNSS bus keeps zumapro's SPI port configuration.
|
The two things that were still open, and the kernel side:
That makes four boots by the unit on the in-tree drivers and three confirmed stops at |
…k on the in-tree drivers
|
The last open item, texts on these drivers (2026-11-09, 20:40 MST, a sixth boot of So on the published kernel's own drivers the 9a has now done: registration, a call, texts both ways, data, GNSS fixes, and confirmed stops, with the NV partitions unchanged. One related fix went to #590 rather than here, because it is in #372's starter: the start now loads |
|
Thank you for this. It closes exactly the gap I pointed at on #590, and it does so cleanly: paths instead of labels so the base needs no symbols, the modules kept behind the guards with the test extended to the two GNSS ones, and the check on a boot with the unit masked that none of the five loaded. The finding about the GNSS bus (60 and 4 byte pieces on gs101's compatible, none with zumapro's) is the kind of thing that saves the next person a week; thank you for carrying it to kernel #237. I checked the Pixel 7 Pro side: the two GNSS modules match compatibles that no device tree in Three things before I merge:
On the version: you were right to leave it. I'll set it at merge; this one takes device-tegu 0.2.11, and #372 and #590 follow. If you have a |
… kernel and attendance as they were The descriptor's comment names the kernel the overlay needs (the modem node of linux-omarchy-mobile#187) and how an older DTB fails. Section P no longer calls its kernel the published one: it was the tip plus four things then open, two of them merged since. It lists the six boots with their times from the journal and who was at the palmtop for each (the first two: nobody), and says what the overlay does on the owner's daily kernel: it doesn't apply, and the starter takes the bring-up modules.
|
All three are in (6e4f8e7).
The |
|
Thank you. All three are answered the way I hoped: the descriptor now says which kernel the overlay needs and how an older one fails, section P says plainly what the test kernel was, and the record of who was there for each boot is exact, including the part that isn't comfortable to write down. The answer about build #100 settles my question too: the overlay doesn't apply there, nothing changes for the owner's daily kernel, and the starter keeps taking the bring-up modules. I merged it onto today's main here (it is clean beside #274's config line and #372's package changes), ran the package's tests on the result, and compiled and applied the overlay again: it applies to a DTB from today's tree and fails on the tagged one exactly as your comment says. I'm merging this first, as device-tegu 0.2.14. That number matters now: kernel #237 put the GNSS nodes into the tree today, so the two new blacklist lines have to reach the phones with the config line. One small thing for your next push to #590 rather than a new one here: section P says #274 is still open and that a tree build has no PHY driver until it lands. It was merged a few minutes before your commit, so after this merge a 9a built from the tree has everything the in-tree start needs. Please bring that sentence up to date together with the DEVICES cells. The smoke report from a boot with the overlay and the unit masked is still welcome whenever the palmtop is next on that kernel. |
Main moved since this branch was cut, and the branch set no number of its own, so the squash would have shipped its changes under a version phones already have. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…ig lines are merged derekross#274 (the PCIe PHY's config line) and derekross#594 (the modem-cpif overlay and the GNSS link driver's config line) are in, so the 9a's Modem and GNSS cells no longer call them "in review" or warn about a tree build without the PHY's driver, and section P says a kernel built from the tree now has everything the in-tree start needs. omamobile-device-tegu 0.2.15, one above main.
|
The phone-smoke: teguKernel
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, omamessages 0.2.2-1, omamobile-apps 0.2.2-1, omamobile-audio 0.5.13-1, omamobile-device-tegu 0.2.17-1, omamobile-fingerprint 0.1.8-1, omamobile-firstboot 0.1.0-1, omamobile-gnss 0.2.8-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-mmd 0.1.4-1, omamobile-modem 0.1.17-1, omamobile-modem-sit 0.3.36-1, omamobile-omarchy 0.1.37-1, omamobile-owl-widgets 0.1.2-1, omamobile-sensors 0.2.1-1, omamobile-shell 0.2.101-1, omamobile-telephony-tegu 0.1.0-1, omaphone 0.2.3-1, omarchy 4.5.0-3, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1.1 The required checks pass. The rows that don't are the palmtop's bring-up state meeting this kernel, not the overlay: the three failed units are the palmtop's own bring-up units (not in the repository), |
…a's modem-cpif overlay and GNSS link driver (derekross#594) Adds device/tegu/overlays/modem-cpif.dtso to the Pixel 9a's DTB_OVERLAYS (it needs a kernel with linux-omarchy-mobile#187), CONFIG_EXYNOS_GNSS_IF_SPI=m to the shared fragment (two modules that bind only to the 9a's nodes), and gnss_spi and gnssif to the 9a's guards, so they don't load by themselves now that the kernel has the 9a's GNSS nodes (linux-omarchy-mobile#237). Nothing here starts the modem; that stays derekross#372's opt-in unit. MODEM-PLAN records six boots on the owner's palmtop on 2026-11-09, on the published kernel tip plus kernel derekross#224, derekross#236, derekross#237 and derekross#274's config: registration, a call, texts, data, GNSS fixes and confirmed stops, with the NV partitions unchanged. The Pixel 7 Pro gains two modules that never load. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A 9a built from the tree can't start its modem from the kernel's own drivers: the board's device tree (kernel #187) has the
modemnode under the PCIe link and nocpifnode, as you pointed out on #590, soomamobile-tegu-modem-up(#372) could only take its bring-up branch. This brings the missing pieces, and the first runs of the in-tree branch through the starter.What changes
device/tegu/overlays/modem-cpif.dtso: the published form of the bring-uptegu-modem-cpif.dtso. It disablespcie@12100000/modemfor the link driver and adds CPIF'scpifandcp-shmemnodes. Paths instead of labels and no references into the base tree, sofdtoverlayneeds nothing of the base DTB's symbols, and the bring-up activation module isn't needed.device/tegu/device.conf(and the package's copy):DTB_OVERLAYS="modem-cpif".kernel/configs/omamobile.config:CONFIG_EXYNOS_GNSS_IF_SPI=m, the GNSS link driver from kernel omamobile-omarchy 0.1.18: the lock clock follows the bar's 12/24-hour setting #185.omamobile-device-tegu's guards:gnss_spiandgnssifblacklisted next to CPIF's modules. With the GNSS nodes in the device tree, udev loaded both on a boot without the modem; they are of use only with the modem up, and the starter loads them by name after CPIF. No version bump, since three open PRs already claim the next numbers; say which you want.Binding CPIF powers nothing, its modules stay blacklisted, and nothing here starts the modem: that is still #372's unit, opt-in.
Tested on the palmtop (2026-11-09,
7.3.0-rc6-omamobile-push1-g773b4102f5ec:omamobileatabcd6aac51cfplus kernel #224, kernel #236 and the 9a's GNSS nodes, built with defconfig, this config and #274'sCONFIG_PHY_ZUMA_PCIE=m; the published DTB with this overlay; #372's boot unit enabled; on the charger, watched over SSH, the owner away for the first boot):/dev/umts_ipc0and/dev/gnss_ipcthere, no UFS error-handler pass, Wi-Fi up beside it.systemctl reboots with the modem up: "CP OFFLINE", "modem stopped (success, the CP OFFLINE before the daemons went)", the latch removed. A boot with the unit masked started nothing and left no latch.Not run yet: a boot without the modem on the package with the new guard lines (the check that the two GNSS modules no longer autoload), and a call on these drivers. Both are next, and I'll add them here.
tools/pr-check,tests/device-overlays,tests/stage-boot-filesand the package'stest/allpass. The record is in MODEM-PLAN, after section P.