drm_gem_map_detach(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_gem_map_detach(9) — like, the Kernel API Manual page, but make it make sense 🫶

okay so bestie, you're in the Kernel API Manual and today's main character is drm_gem_map_detach(9). yes it's a function page. yes it's about dma_buf detach for GEM. no you may not skip it. sit down, hydrate, let's go 💖

✨ NAME ✨

drm_gem_map_detach — the dma_buf detach implementation for GEM, and honestly? she's the cleanup queen we all need 🌸

🌈 SYNOPSIS 🌈

void drm_gem_map_detach (struct dma_buf *dma_buf , struct
       dma_buf_attachment *attach );

that's it. that's the whole signature. void return, no drama, no return value to obsess over 🎀

🦋 ARGUMENTS 🦋

  • dma_buf — the buffer you're detaching from. like, the thing being left behind 😭
  • attach — the attachment that's getting detached. she's the one packing her bags 💅

⭐ DESCRIPTION ⭐

so here's the tea 🌸: this calls drm_gem_object_funcs.pin for the device-specific handling — that's the little hook where your driver gets to do its own thing, iykyk.

then it cleans up the dma_buf_attachment that came from drm_gem_map_attach. like, the messy post-hangout cleanup energy. leaving no crumbs 🧚

and the slay part: you can literally use this as the dma_buf_ops.detach callback. drop it in, it just works. iconic 👑

🔥 SEE ALSO 🔥

okay this list is long and I respect it so much. every single one, no skips, periodt:

fr fr, go read the drm_prime.c overview if you want the whole lifetime-rules lore. that's where the backstory lives 💀

and that's the page, bestie ✨ this one's brought to you straight out of ./drivers/gpu/drm, dated October 2026 — so go forth, detach those dma_buf_attachments responsibly, and remember: cleanup is a love language 💜🎀🦋

📦 where this page comes from