dwc2_hs_pmap_schedule(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dwc2_hs_pmap_schedule(9) β€” Kernel API Manual era πŸ’…

Okay bestie, welcome to the Kernel API Manual page for dwc2_hs_pmap_schedule(9). The vibe is simple: schedule something on the main high speed schedule, keep the bookkeeping cute, and don’t fumble the index. πŸ’–


✨ NAME ✨

dwc2_hs_pmap_schedule β€” schedule in the main high speed schedule 🌈


πŸŽ€ SYNOPSIS πŸŽ€

int dwc2_hs_pmap_schedule (struct dwc2_hsotg *hsotg , struct dwc2_qh *qh
, bool only_one_period , int index );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • hsotg β€” the HCD state structure for the DWC OTG controller. literally the main character state, no cap.
  • qh β€” the QH for the periodic transfer. it’s giving β€œqueue head bestie” energy.
  • only_one_period β€” if true, we limit ourselves to just looking at one period (aka one 100us chunk). this is used if we’ve already scheduled something on the low speed schedule and need to find something that matches on the high speed one. so it’s the β€œjust one little period, please” switch ✨
  • index β€” the index into qh->hs_transfers that we’re working with. keep your eyes on this one, bestie πŸ‘€

🌸 DESCRIPTION 🌸

Okay so this function’s whole job is to schedule something on the main dwc2 schedule. πŸ’…

We’ll start looking in qh->hs_transfers[index].start_schedule_us. We’ll update this with the result upon success. We also use the duration from the same structure. that’s the little bookkeeping moment, and it’s lowkey important 🫢


πŸ”₯ RETURN πŸ”₯

0 for success or an error code. Upon success, the dwc2_hs_transfer_time specified by index will be updated. so yes, the index gets its glow-up on the success path πŸ’–


πŸ‘‘ SEE ALSO πŸ‘‘


xoxo, your Unix bestie πŸ’œ β€” source/version: ./drivers/usb/dwc2; date: October 2026; page: dwc2_hs_pmap_schedule(9)

πŸ“¦ where this page comes from