Skip to content

device/tegu USB-HOST-PLAN: H2b, H4 and H5 ran on 2026-10-30 - #178

Closed
W4HO-ham wants to merge 2 commits into
derekross:mainfrom
W4HO-ham:tegu-usb-host-results
Closed

W4HO-ham wants to merge 2 commits into
derekross:mainfrom
W4HO-ham:tegu-usb-host-results

Conversation

@W4HO-ham

Copy link
Copy Markdown
Contributor

The three attended steps of the host-mode runbook (#136) ran on the palmtop this morning, and this records them under each step in the plan's own form, with the logs quoted.

  • H2b, gn3 plus the usb-host-pmic overlay (int-gpios only, as agreed on device/tegu: USB-HOST-PLAN, the host-mode setup and its next run #136): the MAX77779 PMIC block probes with its gpa8-0 interrupt, the boost's watchdog is serviced from the SGPIO6 interrupt through kernel CI: fall back to simdjson 5.0.5 while Arch's nodejs can't load the new one #139's driver, the PMIC's interrupt count stays at 0, FUNCTION 0x41 / ICSTAT 0xf1, smoke 19 of 19. Pass. The push had to be made with the repository's own bin/omamobile push from a scratch checkout of main carrying the kit's descriptor, because the kit's local configuration keeps hardware-tool stubs on PATH (its hands-free guard); the plan says so.
  • H4, unbind the charger with the drive attached: host mode came up as on 10-28 (VBUS 5.2 V from the boost, a drive enumerated), then the unbind took the TCPC down with the charger as its device-link consumer, with a WARN in tcpm_port_unregister_pd; VBUS collapsed, the drive dropped, the laptop link never came back, and the swap timer rebooted the palmtop as planned. So the answer to H4's question is no, for that reason rather than the boost's, and the plan turns it into a rule.
  • H5, reset without shutdown with host mode on: the early read on the next boot shows the boost left on at 3 s (FUNCTION 0x43, ICSTAT 0x0f) and off by itself at 61 s with no driver loaded (the RT9470's own 40 s watchdog), and the reworked driver (kernel docs/review: 34 lessons and 3 corrections from the twenty-fifth and twenty-sixth rounds #127) takes the left-on chip over at probe ("JEITA on, watchdog on (0x1)", OTG cleared). Pass. No inline meter was on hand, so the early read stands in for the meter rule's VBUS check, and the plan says that.

H6 (cleanup) has not run; its status paragraph says what is still installed. One unexplained side effect from the boot after H5 is noted in a sentence and left for NOTES. tools/pr-check passes, no identifiers.

H2b: the PMIC block probed with its interrupt line and the boost's watchdog is serviced from it; pass. H4: unbinding the charger takes the TCPC down with it as a device-link consumer, with a WARN in tcpm_port_unregister_pd, VBUS collapses and the link needed the timer's reboot: a rule, not a boost result. H5: a reset with host mode on leaves the boost on; the chip's own 40 s watchdog turns it off with no driver to kick it, and the reworked driver takes the left-on chip over at probe. Also the push method the kit's guard forced, and H6's remaining cleanup.
@derekross

Copy link
Copy Markdown
Owner

Thank you for running all three attended steps and writing them up under each step in the plan's own form. H2b's interrupt path and H4's device-link finding (unbinding the charger takes the Type-C port down with it) are both clear, and turning H4 into a rule is the right call.

One thing in H5: its Expect was VBUS at 0 within the reboot, and the early read shows the boost still on at 3 s and off by itself somewhere before 61 s. That's inside the meter rule's two minutes, so stopping wasn't needed, but it's the opposite of the Expect. Could you write it as "Expect not met: the boost stays on until the RT9470's watchdog drops it, within the stop window", and add to the meter rule that, without a meter, the laptop waits more than 60 s after any crash with host mode on? Also, roughly how long after the reset did the laptop go back in? If it was inside that window, please note it.

Smaller things: which tree the -dirty release was built from (kernel #127 and #139 commits), and whether the kit's device.conf differs from the one on main.

…e tree and the descriptor

H5's result now says the Expect (VBUS at 0 within the reboot) was not met: the boost stays on until the RT9470's watchdog drops it, inside the stop window; the meter rule gains the 60 s wait before the laptop goes back in without a meter, and the record says the laptop went in about 45 s after the reset. The H2b method note names the tree the dirty release came from, how the two drivers were built, and how the kit's device.conf differs from main's.
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

All in at 7a8e973:

  1. H5 now reads "Expect not met: the boost stays on until the RT9470's watchdog drops it, within the stop window" (the Expect was VBUS at 0 within the reboot; the two-minute stop wasn't reached), and the meter rule says that without a meter the laptop goes back in no sooner than 60 s after any crash with host mode on.
  2. The laptop went back in about 45 s after the reset ("resetting now" at 08:02:28 palmtop time, SSH answering at 08:03:14 with uptime 0 min), so inside that window; noted as such, with the boost still on at 3 s and no harm seen (dwc3 enumerated, the gadget came up).
  3. The -dirty release is the run kit's osc2 Image from the gn3 integration tree on maclab (~/tegu/int-dt-20261026/kernel, about fifty local changes); the docs/review: 34 lessons and 3 corrections from the twenty-fifth and twenty-sixth rounds #127 boost driver (6c5d97e18) and CI: fall back to simdjson 5.0.5 while Arch's nodejs can't load the new one #139's SGPIO driver were built out of tree against that build's output into updates/otg and updates/gpio. The kit's device.conf differs from main's: it carries SOC_IDS (main's lacks it, which is why the repository's push tool refused main's descriptor) and the longer bring-up DTB_OVERLAYS list.

@derekross derekross closed this in 48f9fbf Oct 31, 2026
@derekross

Copy link
Copy Markdown
Owner

Thank you, every point is in. I made the no-meter wait two minutes, matching the stop window: the boost was still on at 3 s of uptime, and uptime only starts after the bootloader. Landed on main authored by you.

W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Nov 1, 2026
…e host when the device tree has it

Kernel derekross#168's standalone host is being replaced by derekross#178, which puts the 9a's channel 1 on derekross#156's pcie_gs201 and phy_zuma_pcie. The graphics start picks the host from the node's compatible, and both new modules are kept out of autoload like the old one.
derekross added a commit that referenced this pull request Nov 1, 2026
… 13 notes (#270)

#227 added CONFIG_PCIE_ZUMAPRO=m, a symbol no published or integration
kernel has (it belonged to kernel #168's driver, now superseded by #178's
shared zuma-family host), so merge_config dropped it silently; remove it.

#227 also made sec_acpm built in for the Pixel 9a's USB PHY. On the 7 Pro
that registers the S2MPG13's GNSS rails before the regulator core's 30 s
cleanup, and turns the G1 blacklist into a no-op. That is harmless (the
rails are GNSS-only), but AGENTS and GNSS-PLAN described load timing the
shared kernel can no longer give; they now say so.

device/dodge/NOTES.md still called kernel #115 "in review"; it is closed
and the kernel stays in the contributor's fork, as DEVICES says (#264).


Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
derekross pushed a commit that referenced this pull request Nov 1, 2026
…Ie host (#238)

The graphics start gains a last hang-safe step for the 9a's Wi-Fi: it
picks the PCIe host from the node's compatible (the shared zuma-family
PHY and gs201 host from linux-omarchy-mobile#178, otherwise the older
pcie_zumapro), waits for 0000:01:00.0, then loads brcmfmac and waits for
a wl* interface. It runs only when the host node, the wifi-dma-pool and
the firmware our extractor installs
(updates/brcm/brcmfmac4383-pcie.google,zumapro-tegu.bin) are all present,
and otherwise logs a skip. Each failure is logged and skipped. Tested on
the palmtop on kernel #178 with only the extractor's files: Wi-Fi came up
at boot ("Wi-Fi (wlan0)"), associated and passed traffic.

Closes #238

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross pushed a commit that referenced this pull request Nov 2, 2026
…ing (#307)

The 9a's row after today's merges, with a NOTES entry for the evening's boots that the new cells link to.

- **Wi-Fi, testing to works.** `omamobile-device-tegu` 0.2.4 (#238) starts it at boot now, through the shared gs201 host and zuma PHY (kernel #178 on #156, both in review) and brcmfmac (kernel #56, in review), with only the extractor's firmware. The NOTES entry has the boot, and the three rebinds with Bluetooth up after #178's FLR commit. The kernel parts are still in review, and the cell says so, as the display cells did.
- **Suspend, WIP to testing.** The power key now lights the lock screen on the first press (#268, #275). Thirty attended sleeps and a day of real use with auto-sleep on all woke (SLEEP-PLAN, #284). The cell still says that three test sleeps on 10-28 to 10-30 never woke and that sleep tests stay attended. If you'd rather keep WIP until that hang is understood, I'll revert just the word.
- **Display:** the display DT is merged, and brightness, DPMS off and on and the 60/120 Hz switch now have a dated record (kernel #125's boot, which also checks the panel ID).
- **Charging, Haptics, Torch, NFC:** kernel #161, #96, #104 and #105 are merged.
- **USB net:** the rescue also handles a replug the gadget didn't see (#280).

The NOTES entry lists each boot with its release: Wi-Fi from the package, the power-key wake, the replug, storage idle (kernel #99), the panel ID (kernel #125), the RTC without the PMIC interrupt (kernel #55), and the auto-sleep day. GNSS and Modem stay as they are until the SIM test on Tuesday. Docs only; `tools/pr-check` passes, and the diff has no identifiers.

Closes #307

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…s#178)

Results of H2b, H4 and H5 on the Pixel 9a. Maintainer edit: the laptop goes back in no sooner than two minutes after a crash with host mode on, matching the stop window, because the boost was still on at 3 s of uptime and uptime starts after the bootloader.

Closes derekross#178

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…e OnePlus 13 notes (derekross#270)

derekross#227 added CONFIG_PCIE_ZUMAPRO=m, a symbol no published or integration
kernel has (it belonged to kernel derekross#168's driver, now superseded by derekross#178's
shared zuma-family host), so merge_config dropped it silently; remove it.

derekross#227 also made sec_acpm built in for the Pixel 9a's USB PHY. On the 7 Pro
that registers the S2MPG13's GNSS rails before the regulator core's 30 s
cleanup, and turns the G1 blacklist into a no-op. That is harmless (the
rails are GNSS-only), but AGENTS and GNSS-PLAN described load timing the
shared kernel can no longer give; they now say so.

device/dodge/NOTES.md still called kernel derekross#115 "in review"; it is closed
and the kernel stays in the contributor's fork, as DEVICES says (derekross#264).

Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…Ie host (derekross#238)

The graphics start gains a last hang-safe step for the 9a's Wi-Fi: it
picks the PCIe host from the node's compatible (the shared zuma-family
PHY and gs201 host from linux-omarchy-mobile#178, otherwise the older
pcie_zumapro), waits for 0000:01:00.0, then loads brcmfmac and waits for
a wl* interface. It runs only when the host node, the wifi-dma-pool and
the firmware our extractor installs
(updates/brcm/brcmfmac4383-pcie.google,zumapro-tegu.bin) are all present,
and otherwise logs a skip. Each failure is logged and skipped. Tested on
the palmtop on kernel derekross#178 with only the extractor's files: Wi-Fi came up
at boot ("Wi-Fi (wlan0)"), associated and passed traffic.

Closes derekross#238

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ing (derekross#307)

The 9a's row after today's merges, with a NOTES entry for the evening's boots that the new cells link to.

- **Wi-Fi, testing to works.** `omamobile-device-tegu` 0.2.4 (derekross#238) starts it at boot now, through the shared gs201 host and zuma PHY (kernel derekross#178 on derekross#156, both in review) and brcmfmac (kernel derekross#56, in review), with only the extractor's firmware. The NOTES entry has the boot, and the three rebinds with Bluetooth up after derekross#178's FLR commit. The kernel parts are still in review, and the cell says so, as the display cells did.
- **Suspend, WIP to testing.** The power key now lights the lock screen on the first press (derekross#268, derekross#275). Thirty attended sleeps and a day of real use with auto-sleep on all woke (SLEEP-PLAN, derekross#284). The cell still says that three test sleeps on 10-28 to 10-30 never woke and that sleep tests stay attended. If you'd rather keep WIP until that hang is understood, I'll revert just the word.
- **Display:** the display DT is merged, and brightness, DPMS off and on and the 60/120 Hz switch now have a dated record (kernel derekross#125's boot, which also checks the panel ID).
- **Charging, Haptics, Torch, NFC:** kernel derekross#161, derekross#96, derekross#104 and derekross#105 are merged.
- **USB net:** the rescue also handles a replug the gadget didn't see (derekross#280).

The NOTES entry lists each boot with its release: Wi-Fi from the package, the power-key wake, the replug, storage idle (kernel derekross#99), the panel ID (kernel derekross#125), the RTC without the PMIC interrupt (kernel derekross#55), and the auto-sleep day. GNSS and Modem stay as they are until the SIM test on Tuesday. Docs only; `tools/pr-check` passes, and the diff has no identifiers.

Closes derekross#307

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