qbman_swp_enqueue_direct(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

okay so bestie, you're on the qbman_swp_enqueue_direct(9) page in the Kernel API Manual, and the function is literally called qbman_swp_enqueue_direct. Its whole thing? Issue an enqueue command. slay.

✨ SYNOPSIS ✨

int qbman_swp_enqueue_direct (struct qbman_swp *s , const struct
       qbman_eq_desc *d , const struct dpaa2_fd *fd );

πŸŽ€ ARGUMENTS πŸŽ€

  • s β€” the software portal used for enqueue. It's the portal you're using to do the enqueue, periodt.
  • d β€” the enqueue descriptor. This is the descriptor that tells the enqueue what's up.
  • fd β€” the frame descriptor to be enqueued. This is the frame descriptor getting sent into the enqueue moment.

🌸 DESCRIPTION 🌸

okay so huge heads-up, bestie: fd should only be NULL if the "action" of the descriptor is "orp_hole" or "orp_nesn". Like, those are the only two situations where a NULL fd is allowed. no cap.

For the return vibe: 0 means successful enqueue, and -EBUSY means the EQCR is not ready. That's the whole status report. πŸ’…

πŸ¦‹ SEE ALSO πŸ¦‹

For more qbman lore, peep the kernel file ./drivers/soc/fsl/dpio/qbman-portal.c and all these function besties:


xoxo, your source/version is ./drivers/soc/fsl/dpio, the date is October 2026, and this iconic page is qbman_swp_enqueue_direct(9). bye bestie πŸ’–βœ¨

πŸ“¦ where this page comes from