dpdmai_open(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌈 dpdmai_open(9) β€” Kernel API Manual 🌈

okay bestie, this is the dpdmai_open(9) page from the Kernel API Manual, and it's literally about opening a control session. lowkey important, highkey iconic. πŸ’…


✨ NAME ✨

dpdmai_open β€” Open a control session for the specified object

πŸ¦‹ SYNOPSIS πŸ¦‹

int dpdmai_open (struct fsl_mc_io *mc_io , u32 cmd_flags , int dpdmai_id
, u16 *token );

πŸŽ€ ARGUMENTS πŸŽ€

  • mc_io β€” Pointer to MC portal's I/O object. That's your portal hookup, bestie.
  • cmd_flags β€” Command flags; one or more of 'MC_CMD_FLAG_'. Mix and match those flags.
  • dpdmai_id β€” DPDMAI unique ID. Every object's little name tag.
  • token β€” Returned token; use in subsequent API calls. Keep it safe β€” it's your VIP pass for later.

πŸ’… DESCRIPTION πŸ’…

So this function can be used to open a control session for an already created object, okay? That object may have been declared in the DPL or by calling the dpdmai_create function. Either way, it's already a thing. ✨

This function returns a unique authentication token, associated with the specific object ID and the specific MC portal. This token must be used in all subsequent commands for this specific object. Literally all of them, no cap. πŸ”₯

πŸ’€ RETURN πŸ’€

This section is literally blank, bestie β€” no return values listed here. It's giving mysterious. πŸ’€

🫢 SEE ALSO 🫢

Kernel file ./drivers/dma/fsl-dpaa2-qdma/dpdmai.c β€” and these function besties:


Source/version: ./drivers/dma/fsl-dpaa2-qdma Β· date: October 2026 Β· page: dpdmai_open(9). Bye bestie, go open that session πŸ’–βœ¨

πŸ“¦ where this page comes from