dpaa2_io_service_enqueue_qd(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dpaa2_io_service_enqueue_qd(9) β€” the kernel API manual, bestie edition πŸŽ€

okay so this is a page from the Kernel API Manual, and it's literally about yeeting a frame into a QD. sit down, grab a boba, we're doing this πŸ’–


✨ NAME ✨

dpaa2_io_service_enqueue_qd β€” enqueue a frame to a QD. that's it, that's the whole vibe πŸ¦‹


🌸 SYNOPSIS 🌸

int dpaa2_io_service_enqueue_qd (struct dpaa2_io *d , u32 qdid , u8 prio
, u16 qdbin , const struct dpaa2_fd *fd );

like, five things go in, and an int comes out ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • d β€” the given DPIO service. this is your main character right here πŸ‘‘
  • qdid β€” the given queuing destination id. the u32 of destiny fr fr
  • prio β€” the given queuing priority. a lil u8 that decides who gets in first πŸ’…
  • qdbin β€” the given queuing destination bin. u16, small but mighty πŸ“
  • fd β€” the frame descriptor which is enqueued. this is the frame in question, the actual thing getting yeeted in there πŸ“¦

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea β˜• β€” this function returns 0 for a successful enqueue. slay.

but it can also come back with:

  • -EBUSY β€” if the enqueue ring is not ready. it's giving "not right now bestie" 😭
  • -ENODEV β€” if there is no dpio service at all. like, nothing to enqueue to. tragic πŸ’€

no cap, those are the only three outcomes listed here. the way that it's just vibes and error codes, iykyk 🌈


🧚 SEE ALSO 🧚

the source lives in this kernel file, bestie:

Kernel file ./drivers/soc/fsl/dpio/dpio-service.c

and the whole friend group (go say hi to all of them, okay? 🫢):


and that's the whole page, bestie. every flag, every argument, every error code, all present and accounted for. no details were harmed in the making of this rewrite πŸ’œ

kisses, this page came to you from ./drivers/soc/fsl/dpio, dated October 2026 β€” dpaa2_io_service_enqueue_qd(9), periodt πŸ’…βœ¨πŸŒΈ

πŸ“¦ where this page comes from