STRUCT XHCI_SLOT_CTX(9)

💖 NAME 💖

Okay so this is the manual page for struct xhci_slot_ctx, straight outta the Kernel API Manual, bestie 🎀. The NAME line is just the struct name and a lil dash, so we're keeping it cute and moving on.

✨ SYNOPSIS ✨

Here's the whole struct, copied exactly, no edits, periodt:

struct xhci_slot_ctx {
    __le32 dev_info;
    __le32 dev_info2;
    __le32 tt_info;
    __le32 dev_state;
    __le32 reserved[4];
 };

🌸 Members 🌸

• dev_info — Route string, device speed, hub info, and last valid endpoint. It's giving very busy icon energy 💅
• dev_info2 — Max exit latency for device number, root hub port number. Lowkey important stuff 🦋
• tt_info — tt_info is used to construct split transaction tokens. No cap, that's literally what it does ✨
• dev_state — slot state and device address. Main character field behavior 👑

🔥 Description 🔥

Real talk: this is the Slot Context — section 6.2.1.1. It assumes the HC uses 32-byte context structures. If the HC uses 64-byte contexts, there is an additional 32 bytes reserved at the end of the slot context for HC internal use. Those are the facts, bestie, no cap 💅

🦋 SEE ALSO 🦋

• Kernel file ./drivers/usb/host/xhci.h — and the whole squad: struct xhci_cap_regs(9), struct xhci_op_regs(9), struct xhci_intr_reg(9), struct xhci_run_regs(9), struct xhci_container_ctx(9), struct xhci_ep_ctx(9), and struct xhci_device_context_array(9). Go read them, iykyk 🌈

Sign-off time, bestie: source ./drivers/usb/host, date October 2026, page struct xhci_slot_ctx(9). Bye, hydrate, and stay iconic 💖✨