Skip to content

device/tegu FINGERPRINT-PLAN: the LDO15S rule names SLEEP-PLAN S2's one exception - #164

Merged
derekross merged 2 commits into
derekross:mainfrom
W4HO-ham:fingerprint-plan-ldo15s-s2
Oct 30, 2026
Merged

derekross merged 2 commits into
derekross:mainfrom
W4HO-ham:fingerprint-plan-ldo15s-s2

Conversation

@W4HO-ham

Copy link
Copy Markdown
Contributor

The follow-up promised on #144: SLEEP-PLAN S2 turns LDO15S off for one boot on purpose, with the fingerprint service and anything that starts the trusted app or storageproxyd stopped before the push and until the rollback, and FINGERPRINT-PLAN's risk row said the rail must never be switched off as unused. The row now names that one exception and its precondition, so the two plans agree. Text only.

…ne exception

SLEEP-PLAN S2 (merged as derekross#144) turns LDO15S off for one boot on purpose, with the fingerprint stack stopped; the risk row here said the rail must never be switched off as unused, so the two plans disagreed.
@derekross

Copy link
Copy Markdown
Owner

Thanks for picking this up straight after #144. The Risks row is the right place for it, and it now names the exception and the precondition (the fingerprint service and anything that starts the trusted app or storageproxyd stay stopped from the push to the rollback), which matches SLEEP-PLAN S2's step 3.

Two small things before I merge, both one-line edits:

  1. SLEEP-PLAN's half. SLEEP-PLAN on main still says "FINGERPRINT-PLAN (on <…device/tegu: fingerprint F6c-F10 (works) and GNSS G3's third and fourth tries #138>'s branch) gets the matching note as a follow-up once it is on main" (around line 173). Once this merges, that's no longer true. Could you replace that sentence with something like "FINGERPRINT-PLAN's Risks table names this exception."? Then each plan points at the other.
  2. The reason in brackets. "(F6c still writes secure objects)" is out of date. FINGERPRINT-PLAN's own status line says F0-F10 passed, and the lock screen unlocks by fingerprint. The reason the precondition matters now is that an enrolled template lives in Trusty, so I'd write "(an enrolled template lives in Trusty)" or just drop the bracket. SLEEP-PLAN's step 3 has the same dated reason ("F6c is still writing secure objects … while the calibration question is open"). That was my wording from the device/tegu: SLEEP-PLAN, an audit of the s2idle drain #144 review, sorry, and it would be good to fix it in the same edit.

#166 also adds text to SLEEP-PLAN just above S2. Whichever of the two lands second may need a quick rebase, and I'm happy to do it at merge if so.

…the LDO15S exception

SLEEP-PLAN no longer says FINGERPRINT-PLAN's note is a follow-up on another branch, and both plans give the current reason for keeping the fingerprint service stopped around S2: an enrolled template lives in Trusty, not F6c's secure-object writes.
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Both in at 545e439: SLEEP-PLAN now says "FINGERPRINT-PLAN's Risks table names this exception" in place of the follow-up sentence, and the bracket in FINGERPRINT-PLAN and the reason in SLEEP-PLAN's step 3 both read "an enrolled template lives in Trusty". Whichever of this and #166 lands second, a rebase at merge is fine by me.

@derekross
derekross merged commit 006c81e into derekross:main Oct 30, 2026
2 checks passed
@derekross

Copy link
Copy Markdown
Owner

Thank you. Both are in at 545e439: each plan now points at the other, and both give the current reason. Merged.

W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 1, 2026
On the boot of kernel derekross#164's head the camera drivers loaded from the device tree with nothing by hand, libcamera listed all three cameras and each streamed.
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ne exception (derekross#164)

FINGERPRINT-PLAN's Risks table and SLEEP-PLAN step 3 now point at each
other for the one LDO15S exception, and both give the current reason: an
enrolled template lives in Trusty.

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