i915_gem_ob..._dma_address(9)

✨ NAME ✨

So this is the page for i915_gem_object_get_dma_address — and bestie, it's literally just a wrapper macro for __i915_gem_object_get_dma_address. That's it, that's the whole name section 💅 (and yes, this whole page lives in the Kernel API Manual, iykyk 🎀).

---

🌸 SYNOPSIS 🌸

i915_gem_object_get_dma_address (obj , n );

---

🦋 ARGUMENTS 🦋

• obj — your i915 GEM buffer object, the main character of this whole situation 👑
• n — the page offset, like which page we're pointing at 📍

---

💖 RETURN 💖

It hands you back the bus addresses of the targeted DMA mapped scatterlist. That's the vibe — addresses, plural, bus-flavored ✨

---

🌈 DESCRIPTION 🌈

Okay so here's the why: in order to avoid the truncation of the input parameter (😭 the horror), it checks the page offset n's type from the input parameter before calling __i915_gem_object_get_dma_address. Type check first, then the call — that's the whole flex fr fr.

Also peep __i915_gem_object_page_iter_get_sg and __i915_gem_object_get_dma_address while you're here, they're part of the same little friend group 🫶

---

⭐ SEE ALSO ⭐

Kernel file ./drivers/gpu/drm/i915/gem/i915_gem_object.h — the source of truth, no cap 📁

• i915_gem_object_lookup_rcu(9)
• __i915_gem_object_page_iter_get_sg(9)
• i915_gem_object_page_iter_get_sg(9)
• __i915_gem_object_get_sg(9)
• i915_gem_object_get_sg(9)
• __i915_gem_object_get_sg_dma(9)
• i915_gem_object_get_sg_dma(9)
• __i915_gem_object_get_page(9)
• i915_gem_object_get_page(9)
• __i915_gem_object_get_dirty_page(9)
• i915_gem_object_get_dirty_page(9)
• __i915_gem_object_get_dma_address_len(9)
• i915_gem_object_get_dma_address_len(9)
• __i915_gem_object_get_dma_address(9)
• i915_gem_object_pin_map(9)
• i915_gem_object_unpin_map(9)

---

✨ that's the whole page, bestie ✨ — sourced from ./drivers/gpu/drm/i915/gem, dated October 2026. Slay, go read some other manpages now, mwah 🍓💜