STRUCT DMA_SLAVE_MAP(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 struct dma_slave_map(9) 🌸

okay bestie, so this is a page straight out of the Kernel API Manual β€” yes, the actual kernel, not a vibe. it's about struct dma_slave_map, which is the little matchmaker struct that links a slave device and its slave channel to a parameter that a filter function is gonna use later. it's giving wingman energy, fr fr πŸ’…


✨ NAME ✨

struct dma_slave_map β€” associates slave device and it's slave channel with parameter to be used by a filter function πŸŽ€

like, it's the intro card at the party that says "this device, this channel, and this mysterious param go together, the filter function will know what to do with it" πŸ¦‹


✨ SYNOPSIS ✨

struct dma_slave_map {
    const char *devname;
    const char *slave;
    void *param;
 };

three fields, all main character, no notes πŸ’œ


πŸ’– Members πŸ’–

  • devname β€” name of the device. the actual device name string, lowkey the whole identity of the thing πŸŽ€
  • slave β€” slave channel name. yes that's what it's called, that's the field name, keep it exactly as-is bestie πŸ™ˆ
  • param β€” opaque parameter to pass to struct dma_filter.fn. "opaque" here is not a dig, it literally means the kernel isn't looking inside it β€” it just hands it straight to the filter function and trusts the vibes 😭

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./include/linux/dmaengine.h β€” and then, bestie, brace yourself, the whole friend group showed up:

that's not a SEE ALSO, that's a whole groupchat roll call πŸ”₯ read them all, they're all linked for a reason, iykyk ⭐


ngl, param being void * and described as "opaque" is your reminder that you do NOT get to peek inside it here. the filter function handles that. stay in your lane, respectfully 🫢

and that's the whole page, bestie β€” filed under ./include/linux, dated October 2026, still called struct dma_slave_map(9) even after all this πŸ’€ slay, go read the dmaengine header, mwah πŸ’–πŸŽ€βœ¨

πŸ“¦ where this page comes from