dwc2_gadget_..._ep_disabled(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dwc2_gadget_..._ep_disabled(9) β€” kernel API manual, but make it make sense

okay so bestie, you're reading the page for dwc2_gadget_handle_out_token_ep_disabled β€” which is a whole mouthful, i know β€” from the Kernel API Manual, section 9. yes the title up there is the abbreviated version dwc2_gadget_..._ep_disabled(9), that's just how these pages vibe. stay with me, it's actually slay in here πŸ”₯


✨ NAME ✨

dwc2_gadget_handle_out_token_ep_disabled β€” handles DXEPINT_OUTTKNEPDIS. that's it, that's the whole job. main character energy tbh πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

void dwc2_gadget_handle_out_token_ep_disabled (struct dwc2_hsotg_ep *ep
);

void, no return value, we're just out here handling things. πŸ’…


🌸 ARGUMENTS 🌸

  • ep β€” the endpoint on which the interrupt is asserted. like, the specific EP that's throwing the interrupt at you. that's your girl, go handle her 🫢

πŸŽ€ DESCRIPTION πŸŽ€

okay so this function is the starting point for an ISOC-OUT transfer, and the synchronization is done with the first out token received from host while the corresponding EP is disabled. periodt. ⭐

here's the tea though: the device does not know the initial frame in which the out token will come. like, genuinely no clue. so for this, the HW generates OUTTKNEPDIS β€” that means an out token is received while the EP is disabled. that's literally what the interrupt name is telling you, iykyk. πŸ™ˆ

and upon getting this interrupt, SW starts the calculation for the next transfer frame. so: interrupt hits β†’ software does its little math β†’ next frame gets figured out. that's the whole flow, no cap. πŸ’–


🌈 SEE ALSO 🌈

Kernel file ./drivers/usb/dwc2/gadget.c using all of these besties:

like, that's a lot of friends. click through, they all link somewhere in that same gadget file. 🧚


reminder babe: this page is from ./drivers/usb/dwc2, dated October 2026, and the manpage section is 9 (kernel API, not a command you run in your shell, don't try it at home πŸ’€).

okay that's the whole page!! go read the source, stan dwc2_hsotg_epint, and remember: OUTTKNEPDIS is not a typo, it's just the HW being dramatic. mwah πŸ’œπŸ“βœ¨

πŸ“¦ where this page comes from