amdgpu_irq_create_mapping(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… amdgpu_irq_create_mapping(9)

okay so bestie, this is a page straight out of the Kernel API Manual β€” yes, the Kernel API Manual, we're in the big leagues now πŸŽ€ β€” and it's about amdgpu_irq_create_mapping, which is lowkey one of those tiny functions that makes the whole GPU interrupt situation work. summer job energy.


✨ NAME ✨

amdgpu_irq_create_mapping β€” the function that creates a mapping between domain Linux IRQs πŸ¦‹


🌸 SYNOPSIS 🌸

unsigned int amdgpu_irq_create_mapping (struct amdgpu_device *adev ,
   unsigned int src_id );

like, it takes two things and gives you back a unsigned int. that's the whole vibe.


🫢 ARGUMENTS 🫢

  • adev β€” your amdgpu device pointer, the main character of literally every function in this file πŸ‘‘
  • src_id β€” the IH source id. IH as in Interrupt Handler, iykyk 🌈

πŸ’– DESCRIPTION πŸ’–

so what it does: it creates a mapping between a domain IRQ β€” which is the GPU IH src_id β€” and a Linux IRQ. that's it. that's the function.

and the way you use it is specifically for components that generate a GPU interrupt but are driven by a different driver. the example the manpage gives is ACP, and honestly very demure, very mindful of them to mention it πŸ’…


⭐ RETURN ⭐

returns a Linux IRQ. that's the whole return value. slay.


πŸ¦‹ SEE ALSO πŸ¦‹

the source file lives at ./drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c πŸ“ β€” go read it, it's giving lore.

and here's the whole friend group, no cap, every single one:

that's twenty entries plus the Interrupt Handling one, and yes I counted so you don't have to 😭


ngl the whole page is short but it ate. it's from ./drivers/gpu/drm/amd/amdgpu, dated October 2026, and it's a amdgpu_irq_create_mapping(9) moment fr fr. go map some IRQs bestie, ily πŸ’œπŸŒ·
πŸ“¦ where this page comes from