From 44b4e7e5fadbc78c1bee1c02015d0d0509c17231 Mon Sep 17 00:00:00 2001 From: pi-qdq Date: Tue, 10 Nov 2026 18:41:17 -0400 Subject: [PATCH] docs/axb35: the rear-USB-A and Type-C halves of engine#823 need different things awake Measured on the board 2026-11-10 (BIOS 1.10, rule not installed): the four xHCI functions the keepawake rule matches, plus the two USB4 host routers (0x158d/0x158e) that carry the Type-C ports and that the rule does not match, all in D3cold with the thunderbolt driver bound and four live IRQs. A suspended router with no partner is normal, so this is not a claim that the routers are broken. It is a claim about the gate: a plug into a rear USB-A exercises the shipped rule, a plug into Type-C exercises a path nothing in this repository touches, and the two results must not be read as one. Refs engine#823 --- docs/axb35-usb-ports.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/docs/axb35-usb-ports.md b/docs/axb35-usb-ports.md index d369c08ca..06a985d40 100644 --- a/docs/axb35-usb-ports.md +++ b/docs/axb35-usb-ports.md @@ -70,6 +70,34 @@ addressing something a newer kernel had already fixed. Forcing `power/control=on them `D3cold → D0` and their root hubs' ports appear in `/sys/bus/usb/devices`; `--revert` puts them back. So the mechanism works on this kernel; what has not happened is the plug. +## The two halves of this issue have different fixes, and the rule covers one + +Measured on the board 2026-11-10, BIOS 1.10, a dev boot with the rule not installed: + +``` +0000:c5:00.4 0x1587 xhci_hcd D3cold <- rule matches +0000:c7:00.0 0x1588 xhci_hcd D0 <- rule matches +0000:c7:00.3 0x1589 xhci_hcd D3cold <- rule matches +0000:c7:00.4 0x158b xhci_hcd D3cold <- rule matches +0000:c7:00.5 0x158d thunderbolt D3cold <- the rule does NOT match this +0000:c7:00.6 0x158e thunderbolt D3cold <- the rule does NOT match this +``` + +The **rear USB-A** ports hang off the four xHCI functions the rule matches. The **Type-C** ports hang off the two USB4 host routers +(`0x158d`/`0x158e`), which the rule's device list does not contain, and which are in `D3cold` with the `thunderbolt` driver bound and +four live IRQs. So: + +| half of engine#823 | what has to be awake | does the shipped rule cover it | +|---|---|---| +| rear USB-A | one of `0x1587/0x1588/0x1589/0x158b` | **yes** | +| Type-C | `0x158d`/`0x158e` (USB4 host routers) | **no** | + +**A suspended USB4 host router with no partner attached is normal**, so this is not evidence that the routers are broken - it is evidence +that **one plug test cannot test both halves**: a plug into a rear USB-A exercises the rule, a plug into Type-C exercises a path no change +in this repository has touched. Record the router ids with the capture (`tools/xhci_boot_capture.sh` already records `power_state` per +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". + ## 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