From 2875fff42e47ab3dca0126401a481ab56ee4c656 Mon Sep 17 00:00:00 2001 From: bong-water-water-bong Date: Wed, 11 Nov 2026 10:11:04 -0400 Subject: [PATCH] docs: the AXB35-02 USB limitation goes in the release notes, and the audit's two facts beside it (engine#823) The doc commit of #2046 (6c427c8) on current main. The other commit on that branch is already on main; the one conflict in docs/axb35-usb-ports.md is two sections added at the same place, and both are kept (main's first). Co-Authored-By: Claude Fable 5.2 --- docs/axb35-usb-ports.md | 17 +++++++++++++++++ docs/releases.md | 1 + 2 files changed, 18 insertions(+) diff --git a/docs/axb35-usb-ports.md b/docs/axb35-usb-ports.md index 06a985d40..b0bed1731 100644 --- a/docs/axb35-usb-ports.md +++ b/docs/axb35-usb-ports.md @@ -98,6 +98,23 @@ in this repository has touched. Record the router ids with the capture (`tools/x controller; the two `thunderbolt` functions are worth reading the same way) so a "Type-C still dead" result is read as "the router half is untested" rather than "the keepawake fix failed". +## Two things a 2026-11-10 audit added, both read-only (sysfs and source; no root, no plug) + +`engine#823`'s thread carried the audit in full; the two facts that move the next attempt: + +- **`ec_su_axb35` carries no USB control, in source.** The driver binds on this box (`refcount 0`) and its register map is fans only + (`0x20/0x21/0x23/0x25` modes, `0x30/0x31/0x35…` tachometers). So "the EC path is not exposed to Linux" is narrower than it reads: the EC + driver exists, and nothing in it addresses a Type-C or port-power register. A software fix is therefore not a matter of loading the right + module, and a search for an EC-side switcher should start from `0x38` upwards, where nothing is known. +- **One silent controller had a stale resume in that boot**: `0000:c5:00.4` read `runtime_status=resuming` with `power_state=D3cold` while the + other three xHCI functions were `active`/`D0`. A controller whose resume never completed cannot report a connect on its ports, so when a plug + test is next run, read `runtime_status` as well as `power_state` — a `resuming` that persists is a different fault from an autosuspended + controller, and the keep-awake write may be landing during a transition that never settles. + +Also worth knowing for the same next attempt: the three silent controllers have taken **exactly 0 interrupts** since boot while the awake one has +taken **155,139**, and both USB4 host routers are up (`gen=4`, `authorized=1`, ~1.6k interrupts each) with no trained downstream link — so the +USB4 side is alive at PCI level and the missing thing is below it. + ## What is still owed One device into a rear USB-A or a Type-C port **on a 1bit-OS boot**, checked with `--require-awake` first. If a port is then still diff --git a/docs/releases.md b/docs/releases.md index ec61c5f7a..ffa855693 100644 --- a/docs/releases.md +++ b/docs/releases.md @@ -172,6 +172,7 @@ What ran on **c19** (Strix Halo and QEMU, 1 November) — every gate except the | `sha256sum -c SHA256SUMS`, `sbverify`, module/kernel identity | 3/3 OK, signature OK, one module tree for the shipped kernel | | stick write | device readback `3c3c08c2…` **= the image**, `prepare-stick` 11/11 and `--check` exit 0, `/data` grown to the whole device | | no DwarfStar | **0** `ds4/` files and **0** `hipblaslt` references; the image's catalogue has no `ds4` recipe | +| AXB35-02 rear USB-A and Type-C ports ([#823](https://github.com/1bit-MONSTER/engine/issues/823)) | on this board three of the four xHCI functions autosuspend to `D3cold`, so only the controller behind the front USB-A enumerates; the image ships `91-1bit-xhci-keepawake.rules` to keep the four awake, and **a device on a rear port has not yet been confirmed to enumerate on a 1bit-OS boot**. Check with `tools/xhci_keepawake_check.sh --require-awake` (read-only; verdict `all awake` is the only one a plug test is valid under), mechanism and per-boot captures in `docs/axb35-usb-ports.md` | **What did not run on c19: the hardware boot and the hardware install.** The only hardware evidence in this document is candidate **c18**'s — a different, earlier candidate (`rc-2026-10-31c`): live USB boot with Secure Boot on,