Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
9 changes: 9 additions & 0 deletions device/cheetah/GNSS-PLAN.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion device/dodge/NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 |
Expand Down
3 changes: 0 additions & 3 deletions kernel/configs/omamobile.config
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down