STRUCT MU3H_SCH_TT(9)

💅 struct mu3h_sch_tt(9) — TT scheduling data

okay bestie, so this page is all about struct mu3h_sch_tt from the Kernel API Manual — yes, we're in the mu3h_sch_tt(9) era and honestly it's giving "niche but essential" 💖. It's the TT scheduling data struct, and if you're deep in xHCI MediaTek land, you already know iykyk.

---

✨ NAME ✨

struct mu3h_sch_tt — TT scheduling data, no cap 🎀

---

🦋 SYNOPSIS 🦋

struct mu3h_sch_tt {
    u16 fs_bus_bw_out[XHCI_MTK_MAX_ESIT];
    u16 fs_bus_bw_in[XHCI_MTK_MAX_ESIT];
    u8 ls_bus_bw[XHCI_MTK_MAX_ESIT];
    u16 fs_frame_bw[XHCI_MTK_FRAMES_CNT];
    u8 in_ss_cnt[XHCI_MTK_MAX_ESIT];
    struct list_head ep_list;
 };

look at her. iconic. every field copied character for character, because we do not mess with source code in this house 🙈✨

---

🌸 MEMBERS 🌸

• fs_bus_bw_out — lowkey the ledger for bandwidth already used by FS/LS OUT eps, tracked per each uframes 💫
• fs_bus_bw_in — same vibe check but for FS/LS IN eps, saved per each uframes 🫶
• ls_bus_bw — the bandwidth used by LS eps, one entry per each uframes 🧚
• fs_frame_bw — bandwidth used by FS/LS eps, counted per each FS frames ⭐
• in_ss_cnt — the count of Start-Split for IN eps, literally what it says 💅
• ep_list — the Endpoints using this TT, chillin' in a struct list_head 🎀

---

👑 SEE ALSO 👑

• Kernel file ./drivers/usb/host/xhci-mtk.h — plus struct mu3h_sch_bw_info(9), struct mu3h_sch_ep_info(9), and struct mu3c_ippc_regs(9) 🌈

fr fr go read the header, the structs are all besties and they reference each other 💜

---

and that's the whole page, bestie — main character struct, zero skips, every field accounted for 😭💖

cute little sign-off: this one's from the source at ./drivers/usb/host, dated October 2026 — periodt. 🎀✨