From 5583b491d91408e851ab512ac37804b233c2dca4 Mon Sep 17 00:00:00 2001 From: Derek Ross Date: Sun, 1 Nov 2026 14:55:48 -0500 Subject: [PATCH] kernel config, AGENTS, GNSS-PLAN: follow-ups to #227, and the OnePlus 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 Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d --- AGENTS.md | 2 +- device/cheetah/GNSS-PLAN.md | 9 +++++++++ device/dodge/NOTES.md | 2 +- kernel/configs/omamobile.config | 3 --- 4 files changed, 11 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 2b0fd7c37..e96839430 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -149,7 +149,7 @@ Each entry gives the gotcha, then the reason or the fix. Details are in the link - **regmap takes `max_raw_write` from the bus, not the config, when the map has a bus:** capping it in the driver's `regmap_config` did nothing. The fix belonged in the I2C host. - **The HSI2 SysMMU and S2MPU select by VID, and PCIe (AxID 0x0) and UFS (AxID 0x2) both arrive on VID 0:** translating VID 0 starved storage and wedged the phone. Wi-Fi ships with a restricted DMA pool instead, and the driver refuses VID 0. [WIFI-BATTERY-PLAN](device/cheetah/WIFI-BATTERY-PLAN.md) W4 - **ACPM reads its channel table from APM SRAM, and some channels are unusable** (a type-2 buffer channel with queues in DRAM): skip them rather than failing the probe. DVFS is channel 0, PMIC 2, thermal 9. Upstream supports polling only. [ACPM-PLAN](device/cheetah/ACPM-PLAN.md) -- **The regulator core turns off unused rails that have constraints about 30 s after late init:** load PMIC regulator modules after that, or make sure the rails are claimed. [GNSS-PLAN](device/cheetah/GNSS-PLAN.md) +- **The regulator core turns off unused rails that have constraints about 30 s after late init:** load PMIC regulator modules after that, or make sure the rails are claimed. Since #227 the shared kernel builds `sec_acpm` in (the Pixel 9a's USB PHY needs its S2MPG14 rails at boot), so on the 7 Pro the S2MPG13 rails in the DT register before that cleanup and a `blacklist sec_acpm` does nothing; those rails are GNSS-only (LDO9S-11S, LDO15S, and LDO12S when enabled), so the cleanup only turns off rails nothing uses yet. [GNSS-PLAN](device/cheetah/GNSS-PLAN.md) - **The AoC starts only through Trusty** (`com.android.trusty.gsa.hwmgr.aoc`). The GSA mailbox `START` leaves the A32 held. So Trusty is a dependency of audio and sensors, not just of fingerprint, and it runs at every boot on the integration kernel. - **Fingerprint: nothing writes `persist` or the RPMB without the human's explicit go.** The first `storageproxyd` run (FINGERPRINT-PLAN F4) is irreversible, and `omamobile-fp.service` ships disabled because its first run writes Trusty's secure storage. [FINGERPRINT-PLAN](device/cheetah/FINGERPRINT-PLAN.md) - **Set the Bluetooth address only after powering the controller on:** set on a never-powered controller, the kernel withdrew the index for good. diff --git a/device/cheetah/GNSS-PLAN.md b/device/cheetah/GNSS-PLAN.md index c578fce91..0e66d309e 100644 --- a/device/cheetah/GNSS-PLAN.md +++ b/device/cheetah/GNSS-PLAN.md @@ -123,6 +123,15 @@ have constraints about 30 s after late init. LDO9S-11S are GNSS-only and the ODPM rail names), so that is harmless. G1 avoids it anyway by loading `sec_acpm` after the 30 s. +**Since #227 (2026-11-01) `sec_acpm` is built in** (`CONFIG_MFD_SEC_ACPM=y` +in the shared fragment, for the Pixel 9a's USB PHY), so on a kernel built +from it the S2MPG13 registers at boot, before the 30 s cleanup, as above +harmlessly. The G1 blacklist (`omamobile-g1.conf`) then does nothing, the +start script's `modprobe sec_acpm` succeeds without loading anything, and +`omamobile-gnss status` always finds the `vdd_gnss_core` regulator: "chip +powered" still reads the rail's state, but "not loaded yet" no longer +occurs. The 7 Pro boot of #227's config passed phone-smoke. + ## 3. Userspace (omamobile repo) All of it is the `packages/omamobile-gnss` package (default-off; it moved diff --git a/device/dodge/NOTES.md b/device/dodge/NOTES.md index 557ee8193..e725debdb 100644 --- a/device/dodge/NOTES.md +++ b/device/dodge/NOTES.md @@ -43,7 +43,7 @@ and [BRINGUP-M1.md](BRINGUP-M1.md) §4 / §6. | Block | Status | Notes | | --- | --- | --- | -| Boot | testing | Omarchy on `boot_b` (2026-10-28); stock `boot_a` kept; GPT bit 54 marked by hand (kernel in review, [#115](https://github.com/derekross/linux-omarchy-mobile/pull/115)) | +| Boot | testing | Omarchy on `boot_b` (2026-10-28); stock `boot_a` kept; GPT bit 54 marked by hand (kernel in the contributor's fork; [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed) | | Storage | testing | UFS; guard allowlists `boot_b` and `userdata` (shared `initramfs/init`) | | Display | testing | Samsung panel through msm/dpu; brightness and DPMS; warm-boot drop fixed (QTB read) | | GPU | testing | Adreno 830 (gpu2); glmark2 / Freedreno on the phone; Vulkan untested | diff --git a/kernel/configs/omamobile.config b/kernel/configs/omamobile.config index 422fc6a45..4bf051aef 100644 --- a/kernel/configs/omamobile.config +++ b/kernel/configs/omamobile.config @@ -146,9 +146,6 @@ CONFIG_BATTERY_MAX77779=m CONFIG_CHARGER_MAX77779=m # The Pixel 9a's camera power: the RT6160 buck-boost behind the main camera CONFIG_REGULATOR_RT6160=m -# The Pixel 9a's PCIe channel-1 host for Wi-Fi: a module, loaded by the -# device package's hang-safe start, never built in (it would probe at boot) -CONFIG_PCIE_ZUMAPRO=m # The Pixel 9a's TAS2572 speaker amplifiers (tas2781 driver), loaded by the # AoC start once the AoC is online CONFIG_SND_SOC_TAS2781_I2C=m