usb_ep_fifo_status(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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

okay bestie, welcome to the Kernel API Manual page for usb_ep_fifo_status(9) β€” the way that this call just returns a number of bytes or an error is literally giving main character energy. no cap. 🫢

πŸ’– NAME πŸ’–

usb_ep_fifo_status β€” returns number of bytes in fifo, or error. that's the whole vibe check, bestie. ✨

πŸŽ€ SYNOPSIS πŸŽ€

int usb_ep_fifo_status (struct usb_ep *ep );

🌸 ARGUMENTS 🌸

  • ep β€” the endpoint whose fifo status is being checked. this is the endpoint you're side-eyeing, bestie. πŸ‘€

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so FIFO endpoints may have "unclaimed data" in them in certain cases, such as after aborted transfers. 😭 hosts may not have collected all the IN data written by the gadget driver (and reported by a request completion). and the gadget driver may not have collected all the data written OUT to it by the host. so drivers that need precise handling for fault reporting or recovery may need to use this call. fr fr. πŸ› οΈ

the good news: this routine may be called in interrupt context. πŸ’…

this returns the number of such bytes in the fifo, or a negative errno if the endpoint doesn't use a FIFO or doesn't support such precise handling. that's the tea. 🍡

🌈 SEE ALSO 🌈

go read these next, bestie β€” the whole squad is here: 🫢


signed off from source/version ./drivers/usb/gadget/udc, dated October 2026, page usb_ep_fifo_status(9) β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from