dma_heap_add(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dma_heap_add(9) β€” like, the kernel API manual, but make it make sense πŸŽ€

Hey bestie, so this is dma_heap_add(9) from the Kernel API Manual (section 9, iykyk), and honestly? It's giving "one job, does it well." ✨


🌸 NAME 🌸

dma_heap_add β€” adds a heap to dmabuf heaps

No cap, that's the whole thing. It adds a heap. To the dmabuf heaps. Slay. πŸ’–


✨ SYNOPSIS ✨

struct dma_heap * dma_heap_add (const struct dma_heap_export_info
*exp_info );

So the way this works is: you hand it one pointer, you get back a struct dma_heap *. That's it. That's the vibe. πŸ¦‹


🫢 ARGUMENTS 🫢

  • exp_info β€” the info the kernel needs to register this heap. Literally the whole "who am I, what am I, please put me in the heap list" package. Everything it needs to know about your heap lives in here, bestie. πŸŽ€

πŸ‘‘ SEE ALSO πŸ‘‘

  • The kernel file ./drivers/dma-buf/dma-heap.c β€” go read it, it's literally where the magic happens, no cap πŸ”₯
  • struct dma_heap(9) β€” the thing you get back, iconic struct energy
  • dma_heap_get_drvdata(9) β€” grab that driver data
  • dma_heap_get_name(9) β€” grab that name

ngl, this one is short and sweet β€” but every flag, every pointer, every path is in here fr fr. Don't @ me. πŸ’…

And that's a wrap, bestie! 🌈 This lil' page came from the source/version <bold>./drivers/dma-buf</bold> and it's dated <italic>October 2026</italic> β€” so go forth and register your heaps, you absolute main character. Periodt. πŸ‘‘πŸ’œπŸ“

πŸ“¦ where this page comes from