DRM_GEM_DMA..._DUMB_CREATE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… DRM_GEM_DMA_DRIVER_OPS_WITH_DUMB_CREATE β€” like, the DMA GEM driver ops one

okay bestie, welcome to the Kernel API Manual ✨ this one's a macro, it lives in ./include/drm/drm_gem_dma_helper.h, and honestly it's giving "shortcut queen" energy πŸ‘‘


🌸 NAME 🌸

DRM_GEM_DMA_DRIVER_OPS_WITH_DUMB_CREATE β€” DMA GEM driver operations πŸŽ€


✨ SYNOPSIS ✨

DRM_GEM_DMA_DRIVER_OPS_WITH_DUMB_CREATE (dumb_create_func );

literally one argument, that's it, she's low-maintenance πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dumb_create_func β€” the callback function for .dumb_create, no cap. that's the whole job bestie 🫢

πŸ‘‘ DESCRIPTION πŸ‘‘

so the way this works: this macro is your little shortcut for setting the default GEM operations inside the drm_driver structure. one line, all the defaults, slay ✨

but here's the tea β˜• β€” this macro is a variant of DRM_GEM_DMA_DRIVER_OPS, specifically for drivers that override the default implementation of struct rm_driver.dumb_create. iykyk 😌

bestie, listen β€” use DRM_GEM_DMA_DRIVER_OPS if possible. fr fr. this one's only for when you're actually overriding stuff πŸ™ˆ

and if your driver needs a virtual address on imported buffers, then you should be using DRM_GEM_DMA_DRIVER_OPS_VMAP_WITH_DUMB_CREATE instead. different macro, different vibe, don't mix them up 😭


⭐ SEE ALSO ⭐

like a whole friend group of related functions, go say hi to all of them πŸ’–


mwah πŸ’‹ that's the whole page! this one came out of ./include/drm, dated October 2026, and the page itself is DRM_GEM_DMA..._DUMB_CREATE(9) β€” go forth and configure your dumb buffers, bestie, you're gonna eat πŸŒˆπŸ¦‹πŸ’œ

πŸ“¦ where this page comes from