omap_gem_pin(9)

💖 omap_gem_pin — a Kernel API Manual moment 💖

okay so bestie, welcome to omap_gem_pin(9), straight out of the Kernel API Manual. this is the function you call when you need your GEM object to stay put in memory. very main character energy, no cap.

---

✨ NAME ✨

omap_gem_pin — pin a GEM object in memory 🎀

---

✨ SYNOPSIS ✨

int omap_gem_pin (struct drm_gem_object *obj , dma_addr_t *dma_addr );

---

✨ ARGUMENTS ✨

• obj — the GEM object, the whole reason we're here 💅
• dma_addr — the DMA address 🦋

---

✨ DESCRIPTION ✨

so what this does is: it pins the given GEM object in memory, and then it fills the dma_addr pointer with that object's DMA address. that's the whole vibe. 🫶

and the juicy part — if the buffer is not physically contiguous, it will be remapped through the TILER so you get a contiguous view instead. literally the TILER out here doing the most so things line up. slay 🔥

pins are reference-counted, meaning calling this function multiple times is allowed — as long as the corresponding omap_gem_unpin calls are balanced. ok so that's the rule, fr fr: pin it, then unpin it the same number of times. don't leave your pins unbalanced or it's giving 💀.

quick vibe check: returns 0 on success, or a negative error code otherwise. so if you get a negative number back, that's your cue to look away slowly 🙈

---

🌈 SEE ALSO 🌈

• kernel file ./drivers/gpu/drm/omapdrm/omap_gem.c
• omap_gem_fault(9)
• omap_gem_dumb_create(9)
• omap_gem_dumb_map_offset(9)
• omap_gem_unpin_locked(9)
• omap_gem_unpin(9)

---

and that's the page, bestie 💜 this little slice of the Kernel API Manual came from ./drivers/gpu/drm/omapdrm, dated October 2026, and it's titled omap_gem_pin(9) — periodt. 🎀✨