Skip to content

kernel config: the Pixel 9a's USB at boot, battery and charger, camera regulator, Wi-Fi host and speaker amplifiers - #227

Merged
derekross merged 5 commits into
derekross:mainfrom
W4HO-ham:kernel-config-eusb2
Nov 1, 2026
Merged

derekross merged 5 commits into
derekross:mainfrom
W4HO-ham:kernel-config-eusb2

Conversation

@W4HO-ham

@W4HO-ham W4HO-ham commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

The kernel config fragment gets the options the Pixel 9a needs, one commit each:

  • USB at boot: build in the eUSB2 PHY and the PMIC path that powers it (ACPM, the APM mailbox, the S2MPG14 driver).
  • Battery and charger: the MAX77779 fuel gauge and charger, as modules.
  • Camera: the RT6160 regulator in the main camera's supply chain, as a module.
  • Wi-Fi: linux-omarchy-mobile#168's zumapro PCIe channel-1 host, as a module.
  • Speakers: the TAS2572 amplifiers' tas2781 I2C driver, as a module.

USB at boot

A kernel built from kernel/configs/omamobile.config on top of defconfig, as bin/omamobile kernel does, boots the Pixel 9a without USB. It came up to the lock screen, but no gadget ever appeared on the host, so there was no SSH and no way back but the buttons.

The cause is four options that defconfig builds as modules. The initramfs loads none (the descriptor's INITRAMFS_MODULES is empty for tegu), and the fragment's own rule is "M1 essentials built in, so the initramfs needs no modules":

  • CONFIG_PHY_SNPS_EUSB2: the 9a's USB 2.0 goes through a Synopsys eUSB2 PHY.
  • CONFIG_EXYNOS_MBOX, CONFIG_EXYNOS_ACPM_PROTOCOL, CONFIG_MFD_SEC_ACPM: the PHY's rails come from the S2MPG14 PMIC, which Linux reaches only through ACPM over the APM mailbox. Without them the PHY waits for its supplies.

I found these by comparing against the integration config the palmtop runs every day. Only these four were built in there and built as modules here, among the USB, PHY, PMIC, ACPM and Exynos options.

Tested on the palmtop with linux-omarchy-mobile#96's head (5628f188), built natively with the same steps as bin/omamobile kernel: defconfig, then this fragment, then olddefconfig. There is no 9a fragment.

  • With only the eUSB2 PHY built in: still no USB.
  • With all four: USB networking and SSH 60 s after the reboot, release 7.3.0-rc6-omamobile-push1-g5628f1888904.

On that boot the display (DSI-1, 1080x2424) and the GPU (panthor render node) came up through the 9a package's graphics start. The evidence is on #96.

The other four

  • Gauge and charger: both drivers are merged in the kernel but were off in the fragment. With them, a boot of the charger device tree shows both supplies, and charge inhibit works.
  • RT6160: with it, linux-omarchy-mobile#164's cameras power up and all three stream.
  • PCIe host: a module because the device package's hang-safe start loads it; built in, it would probe at boot without the marker. It stays off until Contributor phones: pacman -U fails when [omamobile] is signed with a local key #168 merges.
  • TAS2572: the device package's AoC start loads it once the AoC is online (linux-omarchy-mobile#162).

The testing rows behind each are in #244.

Other phones: the 7 Pro and the 6 Pro already worked with the first four as modules, and building them in costs them only a little kernel size. The ACPM pair is the same code their PMICs use. Once this lands, the same four lines in #240's device/tegu/kernel.config can go.

…s powered through

A kernel built from omamobile.config booted the 9a without USB: the eUSB2 PHY was a module, and the PHY's rails come from the S2MPG14 PMIC through ACPM and the APM mailbox, also modules. The initramfs loads no modules, so USB never came up. With the four built in, a build of linux-omarchy-mobile#96 boots with USB networking and SSH.
Both drivers are merged in the kernel but were off in the fragment, so a kernel built from it had no battery or charger on the 9a. With them as modules, a boot of the charger device tree shows both supplies, and charge inhibit works.
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Added a second commit: CONFIG_BATTERY_MAX77779=m and CONFIG_CHARGER_MAX77779=m. Both drivers are merged in linux-omarchy-mobile, but the fragment never turned them on, so a kernel built from it has no battery or charger on the 9a. I tested it on the palmtop today with #96 + #119 + a charger node (tegu-dt-charger, a PR follows): max77779-battery (capacity 89) and max77779-charger (bound at 1-0069, online, charge_behaviour [auto] inhibit-charge) both appear. Writing inhibit-charge turns the charger and the battery to Not charging, and auto brings Charging back.

The main camera's supply chain includes an RT6160, whose driver was off in the fragment. With it, linux-omarchy-mobile#164's cameras power up and all three stream.
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Third commit: CONFIG_REGULATOR_RT6160=m, which the main camera's supply needs. With it, linux-omarchy-mobile#164's device tree brings all three cameras up on the palmtop from the device tree, and cam -l lists them. 1280x960 frames come in at about 19 fps from the main camera and 30 fps from the ultrawide and the front.

linux-omarchy-mobile#168's pcie_zumapro, as a module: the device package's hang-safe start loads it, and built in it would probe at boot without the marker.
The tas2781 I2C driver drives the 9a's two TAS2572s; the device package's AoC start loads it once the AoC is online (linux-omarchy-mobile#162).
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Two more commits, both tested on the palmtop today:

  • CONFIG_PCIE_ZUMAPRO=m, for linux-omarchy-mobile#168's Wi-Fi host. It's a module on purpose: the device package's hang-safe start loads it, and built in it would probe at boot without the marker.
  • CONFIG_SND_SOC_TAS2781_I2C=m, for the TAS2572 speaker amplifiers on linux-omarchy-mobile#162.

So the fragment now builds everything the 9a's tested rows need: USB, the battery and charger, the cameras, Wi-Fi and the speakers.

@derekross

Copy link
Copy Markdown
Owner

Thank you for tracking this down. A kernel built from our own fragment booting the 9a without USB is exactly what this file should prevent, and the comparison against your integration config was a good way to find the four options. I built the config on today's omamobile: all four stay built in, the rest are modules, and PCIE_ZUMAPRO just waits for linux-omarchy-mobile#168. Two things before I merge. First, the title and the body describe only the first of the five commits, and the title becomes the commit subject when I squash, so could you retitle it to cover the gauge and charger, the camera regulator, the PCIe host and the amplifiers too, with a line per commit in the body? Second, building the ACPM path in changes when ACPM probes on the Pixel 7 Pro (its CPU clocks, thermal sensors and the AoC's rails go through it), so I'll boot the 7 Pro once on a kernel with this fragment before merging. That's on me, not you. Also, h4rkl's #240 adds the same four lines to device/tegu/kernel.config; once this lands those can go.

derekross pushed a commit that referenced this pull request Nov 1, 2026
…its boots (#240)

The second Pixel 9a's record (the phone behind #74): a dated NOTES entry with slot A's state stated once and plainly (stock CP3A.261005.005, live images matching Google's by hash, a recovery boot verified, a full Android boot not), the corrected "not a qualified rollback" line and the `reboot-to bootloader` note, plus `device/tegu/kernel.config`, the fragment those boots ran. The maintainer marked the fragment bring-up only (its shared lines go once #227 lands; touch as a module is a test choice) and gave it the MIT licence line the other fragments carry.

Closes #240

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@W4HO-ham W4HO-ham changed the title kernel config: build in the Pixel 9a's USB PHY and the PMIC path it is powered through kernel config: the Pixel 9a's USB at boot, battery and charger, camera regulator, Wi-Fi host and speaker amplifiers Nov 1, 2026
@W4HO-ham

W4HO-ham commented Nov 1, 2026

Copy link
Copy Markdown
Contributor Author

Retitled to cover all five commits, with a line per commit at the top of the body. Thanks for booting the 7 Pro on it.

@derekross

Copy link
Copy Markdown
Owner

Thanks for the retitle and the line per commit. The title now matches what lands, and the body reads well.

Nothing more is needed from you. The one thing left is mine: building the ACPM path and the APM mailbox in changes when ACPM probes on the Pixel 7 Pro (its CPU clocks, thermal sensors and the AoC's rails go through it), so I'll boot my phone once on a kernel built from this fragment before merging. I'll post the result here.

For later, not for this PR: h4rkl's #240 has merged, so device/tegu/kernel.config on main carries the same four built-in lines (PHY_SNPS_EUSB2, EXYNOS_MBOX, EXYNOS_ACPM_PROTOCOL, MFD_SEC_ACPM). Once this lands they're duplicates there, and I'll drop them in a small follow-up, unless one of you would like to.

@derekross

Copy link
Copy Markdown
Owner

Booted on my Pixel 7 Pro with this fragment (7.3.0-rc6-omamobile-push1-g291da0df9327, the phone's integration kernel plus #164's and #56's shared-driver commits): phone-smoke passes every row (display, GPU, touch, buttons, Wi-Fi, Bluetooth, battery, sound, sensors, cameras, thermal), ACPM and the PMIC probe cleanly with MFD_SEC_ACPM=y, and nothing was cut at the 30 s unused-rail cleanup. CONFIG_PCIE_ZUMAPRO drops out silently until #168's driver lands, as expected. Merging. The four lines #240 added to device/tegu/kernel.config are now duplicates; please drop them in a follow-up.

@derekross
derekross merged commit 053583e into derekross:main Nov 1, 2026
2 checks passed
derekross added a commit that referenced this pull request Nov 1, 2026
… 13 notes (#270)

#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).


Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
wrnu added a commit to wrnu/omarchy-mobile that referenced this pull request Nov 3, 2026
The shared config builds them in since derekross#227, for the Pixel 9a's USB PHY.
Raven's initramfs loads them in order from INITRAMFS_MODULES, so with the
shared config raven's initramfs no longer builds (no exynos-mailbox.ko), and
every raven kernel so far has run them as modules. Built in, the regulator
core's unused-rail cleanup would act on raven's S2MPG10/11 rails before their
consumers load; moving raven to the built-in drivers is its own change, with
its own boot.
derekross pushed a commit that referenced this pull request Nov 3, 2026
Since #227 the shared kernel builds sec_acpm, acpm-protocol and the
Exynos mailbox in, so raven's INITRAMFS_MODULES stopped "omamobile
initramfs" with "no exynos-mailbox.ko" (#391). A module listed in the
build's modules.builtin has nothing to load: it is reported and left
out. A module that is neither a .ko nor built in still stops the build.

The copy loop moves into pack_initramfs_modules so tests/initramfs-steps
can run it on a fake modules tree, as it already does with the init's
steps.

Fixes #391

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
wrnu added a commit to wrnu/omarchy-mobile that referenced this pull request Nov 3, 2026
The shared config builds them in since derekross#227, for the Pixel 9a's USB PHY.
Raven's initramfs loads them in order from INITRAMFS_MODULES, so with the
shared config raven's initramfs no longer builds (no exynos-mailbox.ko), and
every raven kernel so far has run them as modules. Built in, the regulator
core's unused-rail cleanup would act on raven's S2MPG10/11 rails before their
consumers load; moving raven to the built-in drivers is its own change, with
its own boot.
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…its boots (derekross#240)

The second Pixel 9a's record (the phone behind derekross#74): a dated NOTES entry with slot A's state stated once and plainly (stock CP3A.261005.005, live images matching Google's by hash, a recovery boot verified, a full Android boot not), the corrected "not a qualified rollback" line and the `reboot-to bootloader` note, plus `device/tegu/kernel.config`, the fragment those boots ran. The maintainer marked the fragment bring-up only (its shared lines go once derekross#227 lands; touch as a module is a test choice) and gave it the MIT licence line the other fragments carry.

Closes derekross#240

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
…a regulator, Wi-Fi host and speaker amplifiers (derekross#227)

The Pixel 9a's USB at boot, battery and charger, camera and related symbols in the shared kernel fragment. Booted on the Pixel 7 Pro on 2026-11-01 (7.3.0-rc6-omamobile-push1-g291da0df9327): phone-smoke passes every row.
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
…rekross#393)

Since derekross#227 the shared kernel builds sec_acpm, acpm-protocol and the
Exynos mailbox in, so raven's INITRAMFS_MODULES stopped "omamobile
initramfs" with "no exynos-mailbox.ko" (derekross#391). A module listed in the
build's modules.builtin has nothing to load: it is reported and left
out. A module that is neither a .ko nor built in still stops the build.

The copy loop moves into pack_initramfs_modules so tests/initramfs-steps
can run it on a fake modules tree, as it already does with the init's
steps.

Fixes derekross#391

Co-authored-by: Claude Opus 5.5 <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