Skip to content

kernel config: the zuma-family PCIe PHY (CONFIG_PHY_ZUMA_PCIE) - #274

Merged
derekross merged 3 commits into
derekross:mainfrom
W4HO-ham:kernel-config-zuma-pcie-phy
Nov 10, 2026
Merged

derekross merged 3 commits into
derekross:mainfrom
W4HO-ham:kernel-config-zuma-pcie-phy

Conversation

@W4HO-ham

@W4HO-ham W4HO-ham commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

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's pcie_gs201 and phy_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 olddefconfig drops 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_pcie loaded, the link trained at Gen2 x1, and Wi-Fi passed traffic (details on kernel #178). tools/pr-check passes.

…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.
@derekross

Copy link
Copy Markdown
Owner

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. tools/pr-check is clean, CI is green, and the module only binds to google,zuma-pcie-phy, so nothing changes for the Pixel 7 Pro or the other gs201 phones.

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 merge_config drops an unknown one without failing the build. PHY_ZUMA_PCIE only exists on #156 for now.

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.

@derekross

Copy link
Copy Markdown
Owner

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.
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

The condition you set here is met by another route: kernel #156 and #178 were closed, and the PHY driver landed with kernel #187 (c30757a7b, b87e20e89), so config PHY_ZUMA_PCIE is on omamobile today (abcd6aac51cf, drivers/phy/samsung/Kconfig) and merge_config no longer drops the line.

I merged main into the branch and reworded the comment in 56f19e56, since both things you meant to edit at merge are out of date now: it names linux-omarchy-mobile#187 and drops the "until #156 lands" clause, and it says the 9a's modem link uses the same PHY.

Evidence from today on the published tip built with this line (2026-11-09, details on kernel #224 and #594): phy_zuma_pcie loaded, Wi-Fi up on 13120000.pcie at Gen2 x1 and kept through 36 sleeps, and the modem's link on 12100000.pcie up at Gen3 x2 on four boots. Without the line a 9a built from the tree has neither Wi-Fi nor the modem link, so #594's in-tree modem path needs it too.

@derekross

Copy link
Copy Markdown
Owner

Thank you, @W4HO-ham, for coming back to this and for making the two comment
edits I had planned to do myself. The condition is met: PHY_ZUMA_PCIE is on
omamobile now (it came in with linux-omarchy-mobile#187), its dependencies
are all set in our build, so the line stays in the config. CI is green and
the branch merges cleanly onto today's main.

I checked the "nothing changes on other phones" part again against the
published tree. The Pixel 7 Pro has no node for it, so it gains a module that
never loads. The Pixel 8 Pro's device tree does have the PHY and its host
enabled, but its own fragment (device/husky/kernel.config) already builds
this module, so nothing is new there either; that line is now a duplicate and
can go some other time. One thing follows for release kernels, which are built
without the device fragments: from the next one, a Pixel 8 Pro on it gets its
Wi-Fi link at boot as it does on its own builds. I'm fine with that.

Thanks also for the evidence from the published tip (Wi-Fi at Gen2 x1 kept
through 36 sleeps, the modem link at Gen3 x2). Merging.

@derekross
derekross merged commit 29fee6f into derekross:main Nov 10, 2026
2 checks passed
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 10, 2026
…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.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 10, 2026
…, 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.
derekross pushed a commit that referenced this pull request Nov 11, 2026
…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>
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 11, 2026
…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.
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…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.
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants