dpaa2_io_se...iple_desc_fq(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dpaa2_io_se...iple_desc_fq(9) 💅

okay so bestie, welcome to the Kernel API Manual — yes the whole manual, and yes we're reading it together, grab a boba 🧋

✨ NAME ✨

dpaa2_io_service_enqueue_multiple_desc_fq — the icon of enqueueing multiple frames to different frame queues using a whole list of fqids 🎀 (yes, that's the whole job, and she does it flawlessly)

🌸 SYNOPSIS 🌸

int dpaa2_io_service_enqueue_multiple_desc_fq (struct dpaa2_io *d , u32
*fqid , const struct dpaa2_fd *fd , int nb );

like, literally that's the whole call. four args. so clean, so demure 💜

🦋 ARGUMENTS 🦋

  • d — the given DPIO service 💫 this is your main character struct pointer, okay, she's the one doing the work.
  • fqid — the given list of frame queue ids 📋 not one fqid, a whole list of them, plural energy only.
  • fd — the frame descriptor which is enqueued 🎯 this is the thing actually going in.
  • nb — number of frames to be enqueud ✨ yes, "enqueud", we're keeping that spelling exactly, no notes, she's iconic, periodt. this is how many frames we're pushing.

🔥 DESCRIPTION 🔥

Return 0 for successful enqueue — slay, it worked 💖

Return -EBUSY if the enqueue ring is not ready 😭 like she's just not in the mood yet, try again.

Return -ENODEV if there is no dpio service 💀 the vibes are absent, the device is absent, nothing to do here.

ngl the whole function is basically a three-outcome situation: 0, -EBUSY, or -ENODEV. no cap. that's the entire plot 🍓

👑 SEE ALSO 👑

the source file, in all her glory:

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

and the whole friend group, fr fr — every single one of these:

and that's the whole page bestie, you ate that 🫶

cute lil sign-off: this one lives at ./drivers/soc/fsl/dpio and it's dated October 2026 — go off, calendar icon 🌈⭐

📦 where this page comes from