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. 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 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; LDO9S-11S are GNSS-only, and LDO15S (`vdd_udfps`, the fingerprint sensor) and LDO12S (`vddio_cam`, camera I/O) are claimed by their drivers when those load, so the cleanup only turns off rails with no consumer yet. The fingerprint and camera starts' `modprobe sec_acpm` is a no-op there too. [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
3 changes: 2 additions & 1 deletion device/cheetah/GNSS-PLAN.md
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,8 @@ for its own rails). This branch adds S2MPG13 to `sec-acpm` and `s2mps11`
the upstream way, deliberately narrow:

- writes reach only LDO control registers (regmap `wr_table`);
- only LDO9S-11S are in the DT, at stock's ranges (0.725-1.3 V,
- at G1 only LDO9S-11S were in the DT (LDO12S, camera I/O, and LDO15S, the
fingerprint sensor, came later with their own consumers), at stock's ranges (0.725-1.3 V,
1.6-1.95 V, 1.6-1.95 V), so registering them writes nothing;
- the other 25 LDOs exist without constraints and are never touched;
- no interrupt (stock: gpa0-1), no meter, no bucks.
Expand Down