Repository navigation
device/tegu, DEVICES, AGENTS: the 9a on 2026-10-27 and 10-28 - #100
Conversation
|
The red CI here was the flaky audio watchdog test (a race in the test's fake mixer, nothing in this PR). The fix is #107 on its own; I've put the same commit on this branch so CI can pass. Whichever lands first, the other merges clean. |
|
Thanks, @W4HO-ham, this is a big, useful set of notes: the LoCH abort fix for camera switching, the cluster 0 power-down hint resetting the phone (and Google never using it), the MIF numbers in s2idle, and the honest account of where the extra reserved regions come from. The AGENTS.md change checks out against MODEM-PLAN's suspend section. A few things before it merges:
This branch also carries #107's commits. I'll merge #107 first, after which they drop out of this PR's diff by themselves. |
…ff slot A As asked on derekross#100: a dated NOTES line for each claim in the 9a's row that had none (touch sleep fix, Power and RTC wakes, the BCM4383, charger status and inhibit, VPBR, the torch), the display cell back to 60 Hz with 120 Hz in review, the fingerprint wording saying the stores are loop devices of images in userdata, and derekross#28 linked again. MODEM-PLAN no longer sends the SIM to slot A for activation (issue derekross#51).
|
Thanks, all three are in 5c6b52f.
The same commit also fixes MODEM-PLAN's SIM line for issue #51: the SIM is activated elsewhere, not on slot A. |
|
Thanks, @W4HO-ham, all three are done, and the "what the device table's claims rest on" entry is exactly what the table needed: one line per claim, with the release and the kernel PR. I checked the cells against the kernel PRs' states and they match. Two small things:
I'll merge #101 first, since the fingerprint cell links its D1 and F4b steps, and then this one. |
Cameras (the evidence asked for on kernel derekross#63), NFC reading cards, USB-C and host-mode status, UFS clock gating, the fingerprint sensor's rail, the cable-out drain numbers and the recovery buttons, on one tested release. The 9a's DEVICES row now links the kernel PRs each cell rests on, and the NFC gotcha names the release of its 35 s2idle cycles.
Camera switching fixed, pstore, the idle-hint and sleep memory-rate measurements, the cameras' link errors, fingerprint storage and where its calibration lives, and the GNSS rails, with the pull requests in the 9a's row.
… come from As asked on kernel derekross#80: abl@f8800000 is from stock's factory base DTB, the two gaps from the early bring-up's private DRAM map, and what would free them.
…ff slot A As asked on derekross#100: a dated NOTES line for each claim in the 9a's row that had none (touch sleep fix, Power and RTC wakes, the BCM4383, charger status and inhibit, VPBR, the torch), the display cell back to 60 Hz with 120 Hz in review, the fingerprint wording saying the stores are loop devices of images in userdata, and derekross#28 linked again. MODEM-PLAN no longer sends the SIM to slot A for activation (issue derekross#51).
…not keyed by the panel id
5c6b52f to
2f9db1d
Compare
|
Rebased onto |
|
Thanks, @W4HO-ham. The rebase is right: Your record on #125 brings up one more thing for this PR. Two lines here still say stock on slot A "stops in recovery" with Arch on
#125's 10-26 and 10-28 entry shows that Merge order: #125 and this PR both add a section at the top of tegu's NOTES, so they conflict there. I'll merge #125 first. When you rebase this one onto |
|
Thanks, @W4HO-ham. Both lines are right now. The reserved-memory note and the SIM sentence say stock on slot A overwrites The plan stays the same: #125 first, then this one. I tried that order locally. The only conflict is the top of |
…fter, the code by commit The runbook stops if slot B isn't marked successful and doesn't mark it (a devinfo write on the 9a, derekross#125). S1 needs the NFC stop-poll hook active or polling stopped by hand, with the kernel's derekross#131 state and the rule that stays, a Rollback line and pstore after a cycle that doesn't come back. S2 snapshots regulator_summary before and diffs it after, stops if more than the four rails changed, records stock's consumers of them (none in its DT: no phandle on any of the four, the GNSS three on the PMIC's channel mux, LDO15S a spare), keeps the modem off in that boot and stays away from a G3 session. The push wording says what bin/omamobile push writes and that only vendor_kernel_boot differs. The module, the bring-up DT and the S2 change are linked by commit on the fork's tegu-sleep-bringup branch, and the CPU_INFORM hints of 10-28 are credited to the bring-up module that wrote them over the PMU SMC. The measurements link derekross#100's NOTES entry.
* device/tegu: SLEEP-PLAN, an audit of the s2idle drain The 9a sleeps and wakes, but its drain is high. This audits why from stock's device tree and a snapshot of the palmtop: no cluster or SICD idle states, the GNSS and fingerprint rails always on in the bring-up DTB, and MIF, with a measurement runbook. * device/tegu SLEEP-PLAN: the firmware's PSCI has no OS-initiated mode So cluster states on zumapro would be platform-coordinated, with a composite StateID; and the core state's rejection rate, read from cpuidle. * device/tegu SLEEP-PLAN: start from what's measured The cable-out s2idle figure (about 140 mA), MIF in sleep (about 57 mA saved), and the cluster power-down tries of 10-28 (cluster 0 hangs; clusters 1-2 save nothing measurable) were already measured; the candidates are re-ranked on them. * device/tegu SLEEP-PLAN: S2's image, its expectation and rollback * device/tegu SLEEP-PLAN: the review's preconditions, S2's before and after, the code by commit The runbook stops if slot B isn't marked successful and doesn't mark it (a devinfo write on the 9a, #125). S1 needs the NFC stop-poll hook active or polling stopped by hand, with the kernel's #131 state and the rule that stays, a Rollback line and pstore after a cycle that doesn't come back. S2 snapshots regulator_summary before and diffs it after, stops if more than the four rails changed, records stock's consumers of them (none in its DT: no phandle on any of the four, the GNSS three on the PMIC's channel mux, LDO15S a spare), keeps the modem off in that boot and stays away from a G3 session. The push wording says what bin/omamobile push writes and that only vendor_kernel_boot differs. The module, the bring-up DT and the S2 change are linked by commit on the fork's tegu-sleep-bringup branch, and the CPU_INFORM hints of 10-28 are credited to the bring-up module that wrote them over the PMU SMC. The measurements link #100's NOTES entry. * device/tegu SLEEP-PLAN: the fingerprint stack stays stopped in S2's boot, S1's command and column S2 says it turns LDO15S off on purpose for one boot against FINGERPRINT-PLAN's rule (that plan gets the matching note once #138 is on main), and step 3 keeps omamobile-fp, the trusted app and storageproxyd stopped before the push and until the rollback, since F6c still writes secure objects. S1 names its command, power-ab with #157's systemd suspend mode (rtcwake -m no plus systemctl suspend, so the NFC hook runs), reads charge_now, column 7, because the 9a's gauge has no charge_counter, and waits for #157. Also: #125's rules are being settled; the four rails read disabled with or without the unused-rail cleanup; stock's source grepped for the four rail names (DT sources and the register header only, no module asks by name); a Polling read before each run; nothing starts the modem at boot, so nothing to mask.
docs/DEVICES.md: the Pixel 9a row conflicted; this branch's row is the newer status, so it stays.
|
Main moved under this one today (#140 and the afternoon's merges), and DEVICES.md's Pixel 9a row conflicted. I merged main into the branch rather than rebase (e83701a): the only conflict was that row, and this branch's row is the newer status, so it stays; nothing else changed. It should merge cleanly now, and #125, #131 and #136 behind it. |
|
Thanks, @W4HO-ham. Merging One correction to "it should merge cleanly now, and #125, #131 and #136 behind it": that's true against today's One thing for my side, nothing for you to do: taking your 9a row whole was right for everything you'd changed. But it also undid the one cell #140 had touched (Fingerprint, with its link to FINGERPRINT-PLAN). Since #138 landed, both versions are behind the plan anyway: matching and the lock screen work on your kernel now. I'll fix that cell, with the plan link, in my next DEVICES status update. I'll write the squash message myself, so the "Merge main into …" line doesn't land in it. Heads-up for #137: once this is in, it conflicts with this PR's NFC line in AGENTS. The resolution is #137's line with your "( |
# Conflicts: # device/tegu/NOTES.md
Merge main (keep this row over derekross#100's, both NOTES entries). Display no longer claims brightness and the panel's sleep until they have a dated record; charging's kernel derekross#92 is merged, not in review; the Wi-Fi line says kept, not reconnected; the USB cell points at derekross#100's replug record.
… 6-hour auto-sleep series clean, and derekross#100 The shell's own auto-sleep behind the lock, with the fixed kernel: the power-key wake, 30-minute and one-hour sleeps, then a series of twelve half-hour sleeps woken by the RTC, all clean, 15 wakes in the boot with no UFS error. The two scripts arm the alarms and watch from the laptop. derekross#100 adds the modem fixes the test tree had lacked; the sleep path is unchanged.
… 6-hour auto-sleep series clean, and derekross#100 The shell's own auto-sleep behind the lock, with the fixed kernel: the power-key wake, 30-minute and one-hour sleeps, then a series of twelve half-hour sleeps woken by the RTC, all clean, 15 wakes in the boot with no UFS error. The two scripts arm the alarms and watch from the laptop. derekross#100 adds the modem fixes the test tree had lacked; the sleep path is unchanged.
* device/tegu: SLEEP-PLAN, an audit of the s2idle drain The 9a sleeps and wakes, but its drain is high. This audits why from stock's device tree and a snapshot of the palmtop: no cluster or SICD idle states, the GNSS and fingerprint rails always on in the bring-up DTB, and MIF, with a measurement runbook. * device/tegu SLEEP-PLAN: the firmware's PSCI has no OS-initiated mode So cluster states on zumapro would be platform-coordinated, with a composite StateID; and the core state's rejection rate, read from cpuidle. * device/tegu SLEEP-PLAN: start from what's measured The cable-out s2idle figure (about 140 mA), MIF in sleep (about 57 mA saved), and the cluster power-down tries of 10-28 (cluster 0 hangs; clusters 1-2 save nothing measurable) were already measured; the candidates are re-ranked on them. * device/tegu SLEEP-PLAN: S2's image, its expectation and rollback * device/tegu SLEEP-PLAN: the review's preconditions, S2's before and after, the code by commit The runbook stops if slot B isn't marked successful and doesn't mark it (a devinfo write on the 9a, derekross#125). S1 needs the NFC stop-poll hook active or polling stopped by hand, with the kernel's derekross#131 state and the rule that stays, a Rollback line and pstore after a cycle that doesn't come back. S2 snapshots regulator_summary before and diffs it after, stops if more than the four rails changed, records stock's consumers of them (none in its DT: no phandle on any of the four, the GNSS three on the PMIC's channel mux, LDO15S a spare), keeps the modem off in that boot and stays away from a G3 session. The push wording says what bin/omamobile push writes and that only vendor_kernel_boot differs. The module, the bring-up DT and the S2 change are linked by commit on the fork's tegu-sleep-bringup branch, and the CPU_INFORM hints of 10-28 are credited to the bring-up module that wrote them over the PMU SMC. The measurements link derekross#100's NOTES entry. * device/tegu SLEEP-PLAN: the fingerprint stack stays stopped in S2's boot, S1's command and column S2 says it turns LDO15S off on purpose for one boot against FINGERPRINT-PLAN's rule (that plan gets the matching note once derekross#138 is on main), and step 3 keeps omamobile-fp, the trusted app and storageproxyd stopped before the push and until the rollback, since F6c still writes secure objects. S1 names its command, power-ab with derekross#157's systemd suspend mode (rtcwake -m no plus systemctl suspend, so the NFC hook runs), reads charge_now, column 7, because the 9a's gauge has no charge_counter, and waits for derekross#157. Also: derekross#125's rules are being settled; the four rails read disabled with or without the unused-rail cleanup; stock's source grepped for the four rail names (DT sources and the register header only, no module asks by name); a Polling read before each run; nothing starts the modem at boot, so nothing to mask.
…ss#100) Pixel 9a records from 2026-10-27 and 2026-10-28 in tegu NOTES: cameras, NFC, USB-C, storage power, fingerprint and drain on 10-27; camera switching, pstore, idle hints and sleep memory rate on 10-28; and what the device table's claims rest on. MODEM-PLAN, AGENTS and the DEVICES row follow those records. NOTES keeps newest first: the 10-29 section, then the slot A fallbacks from derekross#125, then these three. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This is the tegu notes PR you asked for on kernel #63 and on #72.
cam -l, the smoke-test line, the test-pattern reads and the tested blob ids against DEVICES, README, ROADMAP, AGENTS: hardware status as of 2026-10-26 #63;pr-check passes. No identifiers: the camera lines are DT paths only.