dwc2_hsotg_complete_request(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dwc2_hsotg_complete_request(9)

okay bestie, this is the Kernel API Manual page for dwc2_hsotg_complete_request(9), and it's giving kernel-internals main character energy. Let's get into it. ✨

πŸ’– NAME

dwc2_hsotg_complete_request β€” complete a request given to us. literally the whole point, no cap. πŸ’…

✨ SYNOPSIS ✨

void dwc2_hsotg_complete_request (struct dwc2_hsotg *hsotg , struct
       dwc2_hsotg_ep *hs_ep , struct dwc2_hsotg_req *hs_req , int result );

πŸŽ€ ARGUMENTS πŸŽ€

  • hsotg β€” the device state, like the whole device situation we're working with. 🫢
  • hs_ep β€” the endpoint the request was on. that's its spot. ✨
  • hs_req β€” the request to complete. yes bestie, this one right here. πŸ’…
  • result β€” the result code (0 => Ok, otherwise errno). keep that exactly in mind. πŸ”₯

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so the given request has finished. when that happens, call the necessary completion if it has one, and then look to see if we can start a new request on the endpoint. that's the little routine, bestie. 🫢

🚨 note note note: this expects the ep to already be locked as appropriate. it is not out here doing that for you, iykyk. πŸ’€

🌈 SEE ALSO 🌈

Kernel file ./drivers/usb/dwc2/gadget.c β€” that's the home base. also go peek at this whole friend group:


and that's the page, bestie! 🫢 this cutie lives in ./drivers/usb/dwc2, is dated October 2026, and it's the dwc2_hsotg_complete_request(9) manual page. slay and bye! πŸ’–

πŸ“¦ where this page comes from