Repository navigation
device/tegu: USB-HOST-PLAN, the host-mode setup and its next run - #136
Conversation
The 10-28 host-mode run depended on a DT fragment and an RT9470 boost module that weren't in any public tree. This publishes both as they ran, with what they build on, a gated runbook with the swap timer, and what is still unknown.
…s were covered, and what is still unknown Points from review: the setup is in derekross#136, the cable swaps were attended with per-script dead-man switches, JEITA reading hot is an inference, and the warm-reboot boost state and RT9470 charging are unmeasured.
|
Thanks for publishing this so quickly. Having the fragment and the module public is what I asked for, and the README's "Not known yet" section is exactly the right list. I've read the module, the fragment and the runbook against the code they build on. A few things to settle before the next run, and one about where this lives. Where it lives. CONTRIBUTING §6.1 keeps drivers and device trees out of this repository, even bring-up ones. That's my fault: on #131 I asked you to push "a branch or a draft PR" without saying which repository. Could you move Pieces the setup still needs that aren't public:
The runbook:
The module:
None of this changes how I see the 10-28 result. It's about making the next run safe and reproducible. Once 1-3 are answered and the runbook has steps 4-8, I'm happy for the run to go ahead. The RT9470's upstream shape still waits on my (a) or (b) answer on #124. |
Review: the device tree and the RT9470 module moved to the kernel bring-up branch (derekross/linux-omarchy-mobile#127). This leaves the plan with what the setup builds on, the dead-man and curated autostart explained, a runbook with the unbind and reset-without-shutdown measurements for derekross#124, and the early RT9470 read as a one-boot unit.
|
Thanks. Here's where each point landed: Where it lives. The fragment and the module are on derekross/linux-omarchy-mobile#127, a draft marked bring-up, not for merge, on top of #119. This PR is now
The runbook (H1-H6):
The module:
H4 and H5 wait for W4HO at the palmtop. |
Review: name where the parts are (derekross/linux-omarchy-mobile#127) and where the plan is (derekross#136).
|
Thank you, this is a big improvement. The module and the DT now live on derekross/linux-omarchy-mobile#127, and this PR is a plan with a real runbook. I went through every point against #127 at
The early-read helper is read-only. It uses A few things to settle before H4 and H5 run. They're all runbook text:
Not blocking:
The policy check and CI pass. Nothing here writes outside |
… H5 scripts, the meter rule and rollbacks The maintainer's review of the runbook: H2 now copies and enables the early read (and H6 removes it), H1 checks the I2C device nodes and that the DTB dead-man is unarmed and disables it, the meter rule covers any reset with the drive attached, and H4 and H5 have rollback lines and a word on pstore. H5 says plainly that no SSH is guaranteed after the drive-for-laptop swap, what can bring the link back, and the forced restart that boots like H3. The scripts that run while the laptop is out are published next to the early read and started detached with systemd-run: H4's unbinds the charger 20 s after the drive enumerates and logs VBUS and CHG_CNFG_00; H5's resets without a shutdown, and only when the early read is armed and a drive has enumerated. The early read loads i2c-dev itself, since it runs before systemd-modules-load, and waits for the root to be read-write. The DTB paragraph records the gn3 build's sha256 and that it isn't derekross#127 byte for byte; the node comparison against a derekross#127 build is the open step. "settled on derekross#125" is "being settled".
|
Thanks, all six are in at becf004, plus the two optional ones as far as I could take them.
The DTB paragraph now has gn3's sha256 and says it isn't #127 byte for byte; comparing the three decompiled nodes against a #127 build is the open step, I haven't built one yet. H1 checks the dead-man is unarmed (unit, marker, its log) and disables it; whether it ever fired on 10-28 I'll answer from its log on the palmtop in H1, nothing on the laptop shows a write. |
|
The open step from my last comment is done: I built #127 at 5dd15e31c on maclab (dtbs only, the palmtop's config) and compared its |
… warm reboots, stock's PDO and the RT9470's lines The open step from the review is done: derekross#127's DTB matches the palmtop's running tree on the three nodes. Four warm reboots today came up as peripheral on the otg node. Stock's source PDO and the RT9470's interrupt and enable lines are traced to Google's tegu and zuma trees.
|
Thank you. Every point is in, and so are both of the optional ones. I went through
I also checked the H5 boot claim against A few small things, all text or a line of script. Please fix them in the same push before H5:
With those in, I'm happy for H4 and H5 to go ahead with you at the palmtop, as before. Please put the dead-man log's answer from H1 into the plan when you have it. CI and the policy check pass on |
The RT9470's interrupt and enable are MAX77779 SGPIOs, and stock services the boost's watchdog from that interrupt. The block's driver (kernel derekross#139), the board node and the reworked boost (derekross#127) get one attended boot before H3, with Expect, Stop and Rollback, and the PMIC's register readout from today as the before.
|
One more step in the runbook, at 2e47c15: H2b, the boot that brings in the MAX77779 PMIC block (linux-omarchy-mobile#139) and the RT9470's two SGPIO lines with the boost reworked to keep its 40 s watchdog and service it from the interrupt (the last two commits on linux-omarchy-mobile#127). Attended, with the boost module still blacklisted so the PMIC probes alone first, then the boost loaded by hand; Expect, Stop (an interrupt count that climbs, a pull wrong) and Rollback are in, and the PMIC's register readout from today without the node is recorded as the before. H3 onwards is unchanged. |
…it doesn't reset, the derekross#127 pin, H4's rollback with the drive in The maintainer's second round. The DTB paragraph no longer calls the node comparison open, since the paragraph below records it, and the status line says derekross#127 is at 5ada9ab0f now, with what the commits after the compared 5dd15e31c changed. The H5 script removes the early read's armed marker on every exit without a reset, so a fallback reboot can't leave a log that looks like H5's; H5 says the read counts only when the script's log ends with the "resetting now" line, and gives the swap timer's command in full. H4's rollback with the drive still in points at H5's swap text, since a boot like H3's needs the laptop back in first.
|
All three are in at 0daf676 and the PR is out of draft. The DTB paragraph no longer calls the comparison open and the status line pins #127 at 5ada9ab0f, with what changed after the 5dd15e31c build the diff used (a comment, the boost rework, the PMIC node) and that H2b boots the new build. The H5 script now removes the armed marker on every exit without a reset, H5 says the early read counts only when its log ends with the "resetting now" line, and the timer command is spelled out as in H4. H4's rollback with the drive still in now points at H5's swap text (the rescue unit, then the forced restart with the laptop attached); the dead-man log's answer from H1 goes into the plan when I have it. |
The read-only precondition and the installs need no hands, so they ran over SSH: the dead-man never fired on 10-28 (its log), it is disabled now, and the charger, the reworked boost, the PMIC driver and the helpers are in place for H2b and H3.
The derekross#127 DTB can't take the kit's other overlays (a dry pack failed on the first of them), so H2b's delta, the MAX77779 PMIC node with its pin and the boost's two lines, goes on gn3 as a bring-up overlay, where bring-up overlays live. A dry pack applied it and the overlaid tree has all three pieces.
|
Thank you, @W4HO-ham. All three fixes from my last comment are in, and the H1 and H2 records are a nice bonus. I went through
Thanks also for the dead-man answer: it never fired on 10-28, and it's disabled now. H2 with the modules kept as I also read H2b's driver, derekross/linux-omarchy-mobile#139. Its probe only writes the interrupt mask and acknowledges pending bits, then unmasks the SGPIO source once the interrupt is requested. The TCPC has its own line (gpa8-3), so the USB-C path isn't touched. I compiled the overlay, and node for node it matches #127 at Two things in H2b need changing before it runs, and I'd like them in before I merge, since the plan is what the next person follows:
Smaller things, in the same push if you can:
CI and the policy check pass on |
…nterrupt only, with its way back From Derek's review of 2198e47. The H2b overlay no longer gives the boost its enable line: SGPIO7 is the RT9470's charge enable, and driving it with nothing managing the charger could start it charging beside the MAX77779; that line stays with kernel derekross#127, which must clear CHG_EN before taking it. H2b now reads the boost's FUNCTION and ICSTAT after the modprobe, as the H4 script does, and stops if ICSTAT shows charging. Its rollback says what to do when SSH doesn't come back after a forced restart: fastboot by the buttons and stop, no flash without Derek (derekross#125), so the step is risk medium; the header and the DTB paragraph say that H2b's push writes slot B's images through the normal path. The status line says H2b boots gn3 plus the overlay, step 1 is marked done by H2, the H5 script traps TERM so the swap timer's reboot disarms the early read too, the overlay's header says bring-up only, and the watchdog sentences record the reworked boost driver (6c5d97e18) as the follow-up asked for on derekross#131.
|
All of it is in
Also the follow-up from #131: the "What it builds on" row and the watchdog paragraph in the notes now record that the reworked boost driver on derekross/linux-omarchy-mobile#127 (
|
|
Thank you, @W4HO-ham. Everything from my last comment is in |
…ekross#136) USB-HOST-PLAN for the Pixel 9a: the host-mode setup through TCPM and the gated runbook for its next run. H2b's push is the one slot B write, risk medium, and its way back ends in fastboot by the buttons with no flash without the maintainer. The bring-up overlay leaves the charge enable (SGPIO7) alone; H2b reads FUNCTION and ICSTAT after the modprobe and stops if the phone is charging. The H5 script disarms its early read on a TERM from the swap timer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
As you asked: the device tree and the RT9470 module now live on the kernel bring-up branch derekross/linux-omarchy-mobile#127 (not for merge). This PR is now a plan,
device/tegu/USB-HOST-PLAN.md, plus the one-boot early-read helper indevice/tegu/usb-host/. The plan has what the setup builds on, what the DTB dead-man did and the curated autostart is, and a runbook with the two measurements for #124.