dma_request_chan_by_mask(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dma_request_chan_by_mask(9) β€” from the Kernel API Manual πŸŽ€

okay bestie, welcome to the group chat. this one's from the Kernel API Manual, and it's actually kinda short but it SLAPS. it's literally "gimme a DMA channel that matches my vibe" β€” no cap.


✨ NAME ✨

dma_request_chan_by_mask β€” allocate a channel satisfying certain capabilities πŸ¦‹

like, you hand it a mask of capabilities and it goes off and finds you a DMA channel that actually fits the bill. main character energy fr.


🌸 SYNOPSIS 🌸

struct dma_chan * dma_request_chan_by_mask (const dma_cap_mask_t *mask
);

that's it. that's the whole signature. one argument, one pointer back, iconic.


πŸŽ€ ARGUMENTS πŸŽ€

  • mask β€” capabilities that the channel must satisfy πŸ’–

so basically the mask is you telling the kernel "okay this is the bare minimum bestie, don't come back with anything less." the channel has to satisfy it. periodt.


⭐ DESCRIPTION ⭐

Returns a pointer to the appropriate DMA channel on success β€” or an error pointer 😭

that's the whole thing. success = you got a channel pointer. not-success = you got an error pointer back, so like, do a little vibe check on it (iykyk) before you go dereferencing anything, okay? 🫢


🌈 SEE ALSO 🌈

Kernel file ./drivers/dma/dmaengine.c β€” that's the home base for all of this 🏠

and then the whole extended friend group:

go read them all. or don't. but like, they're there πŸ’€


and that's the whole page bestie β€” no filler, all facts 🧚

this lil dma engine situation lives over in ./drivers/dma, and the docs are dated October 2026. slay, honestly. πŸ’…βœ¨πŸ“

πŸ“¦ where this page comes from