Repository navigation
kernel config: the zuma-family PCIe PHY (CONFIG_PHY_ZUMA_PCIE) - #274
Conversation
…xel 8 Pro's Wi-Fi Kernel derekross#178 puts the 9a's channel-1 Wi-Fi on derekross#156's gs201 host and zuma PHY. Without CONFIG_PHY_ZUMA_PCIE the device package's Wi-Fi step logs "phy_zuma_pcie failed" and Wi-Fi stays off.
|
Thank you, this is exactly the line I asked for on #238, and the test on the palmtop with today's fragment (the PHY loaded, Gen2 x1, Wi-Fi passing traffic) is the right evidence for it. On the merge order: I'll merge this right after linux-omarchy-mobile#156 is in. We've decided that every option in the shared fragment has to exist on the published kernel branch when it lands, because Since that makes the "until #156 lands" clause out of date the moment this merges, I'll make a small edit to the comment then (you've allowed edits): it'll name the kernel repository for #156 and #178, so nobody reads them as numbers in this repository, and drop that clause. Nothing for you to do. Thanks again for following it through to the fragment. |
|
Nothing new to ask here; it still waits on linux-omarchy-mobile#156 landing (the Kconfig symbol isn't on the published branch yet, so merge_config would drop the line silently). I'll merge right after. Thanks for the patience. |
The PHY driver is on the published branch since linux-omarchy-mobile#187, so the line is no longer dropped, and the 9a's modem link uses the same PHY as its Wi-Fi.
|
The condition you set here is met by another route: kernel #156 and #178 were closed, and the PHY driver landed with kernel #187 ( I merged main into the branch and reworded the comment in Evidence from today on the published tip built with this line (2026-11-09, details on kernel #224 and #594): |
|
Thank you, @W4HO-ham, for coming back to this and for making the two comment I checked the "nothing changes on other phones" part again against the Thanks also for the evidence from the published tip (Wi-Fi at Gen2 x1 kept |
…rnal, 42 of 43 stops in the cell, and what the in-tree start needs Three times in 2.9 were wrong (the fifth in-tree boot, the texts' boot and the repeat of the unconfirmed stop, which came nineteen minutes later, not an hour). The section now has a table of the evening's boots with the modem up, taken from journalctl --list-boots and each boot's own lines: when it started, on which kernel, who started the modem, and whether its stop was confirmed. The Modem cell says 42 of 43 stops confirmed with one unexplained, and names derekross#274 next to the overlay as what the in-tree start needs; the GNSS cell says the 9a's GNSS nodes are merged. 2.9's heading no longer calls its kernel the published one.
…, how the test ran, and its second kernel named for what it was The rule covers every way round the inhibitor (suspend -i, rtcwake -m, a write to /sys/power/state), allows only an attended test on the charger that ends in a reboot, and leaves the 7 Pro's to the maintainer. AGENTS says what was seen (the command register at 0xffff), not the untested reading of it. The plan says how the five boots ran: at night, unattended, on the owner's standing word and not a yes per run, so outside the 9a's sleep rule. Its second kernel is named as the published tip plus kernel derekross#224, derekross#236, derekross#237 and derekross#274's config line, not as the published kernel. The script's header says attended and names the last step.
…a's modem-cpif overlay and GNSS link driver (#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 #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 #224, #236, #237 and #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>
…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.
…ross#274) The shared config builds the zuma-family PCIe PHY as a module. The symbol is on the published omamobile kernel since linux-omarchy-mobile#187; the Pixel 8 Pro and Pixel 9a need it for their PCIe links (modem and Wi-Fi). The Pixel 7 Pro gains one module that never loads. Release kernels are built without device fragments, so from the next release kernel a Pixel 8 Pro on it brings its Wi-Fi link up at boot.
…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>
One line for the fragment, as you asked on #238:
CONFIG_PHY_ZUMA_PCIE=m, next to the gs201 PCIe host and PHY. Kernel #178 puts the Pixel 9a's channel-1 Wi-Fi on #156'spcie_gs201andphy_zuma_pcie, and #156 uses the same PHY for the Pixel 8 Pro. Without it, device-tegu 0.2.4's Wi-Fi step logs "phy_zuma_pcie failed" and Wi-Fi stays off.The module binds only to its compatible, so it changes nothing on other phones, and until #156 lands
olddefconfigdrops the unknown symbol, as with the HK3 panel line.Tested: the k178 kernel booted on the palmtop today was built with this line on today's fragment.
phy_zuma_pcieloaded, the link trained at Gen2 x1, and Wi-Fi passed traffic (details on kernel #178).tools/pr-checkpasses.