uaudio_endpoint_setup(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so this is uaudio_endpoint_setup β€” and no cap, its whole thing is fetch and populate endpoint params ✨. Think of it as the function that goes and grabs the endpoint info and fills it in, bestie. Also hiiii, you're reading the Kernel API Manual page for uaudio_endpoint_setup(9) β€” welcome to the group chat 🫢.

✨ SYNOPSIS ✨

       phys_addr_t uaudio_endpoint_setup (struct snd_usb_substream *subs ,
       struct snd_usb_endpoint *endpoint , int card_num , struct mem_info_v01
       *mem_info , struct usb_endpoint_descriptor_v01 *ep_desc );

🌸 ARGUMENTS 🌸

  • subs β€” the usb substream. literally the stream context being handed in πŸ’…
  • endpoint β€” the usb endpoint to add. yes bestie, this is the one getting added ✨
  • card_num β€” the uadev index. it's giving "which card are we talking about" energy πŸŽ€
  • mem_info β€” QMI response info. the QMI response details live here πŸ¦‹
  • ep_desc β€” QMI ep desc response field. this is the endpoint-descriptor field from the QMI response πŸ‘‘

πŸ”₯ DESCRIPTION πŸ”₯

okay so uaudio_endpoint_setup initializes the USB endpoint that's being used for a particular USB stream. that's the main character move 🫢. It will request XHCI sec intr to reserve the EP for offloading, and it also populates the QMI response with the transfer ring parameters. both of those things? yes bestie, same function, iconic behavior πŸ‘‘.

πŸ’œ SEE ALSO πŸ’œ

the kernel file in question is ./sound/usb/qcom/qc_audio_offload.c β€” go read it, iykyk πŸ“š. and these iconic cross-references are all here:


and that's the whole page, bestie πŸŽ€. this Kernel API Manual entry for uaudio_endpoint_setup(9) comes from ./sound/usb/qcom, dated October 2026 β€” slay, bye πŸ’…βœ¨

πŸ“¦ where this page comes from