dm_crtc_high_irq(9)

💅 dm_crtc_high_irq(9) 💅

okay so bestie, welcome to the kernel API manual for dm_crtc_high_irq — she lives in the kernel docs (that's the manual name, iykyk) and she is literally the moment a CRTC interrupt gets handled. iconic behavior honestly.

---

✨ NAME ✨

dm_crtc_high_irq — handles CRTC interrupt 🎀

---

🌸 SYNOPSIS 🌸

void dm_crtc_high_irq (void *interrupt_params );

that's it. that's the whole signature. no cap. 🫶

---

🦋 ARGUMENTS 🦋

• interrupt_params — used for determining the CRTC instance. that's her whole job, fr fr 💅

---

🔥 DESCRIPTION 🔥

okay so picture this: an interrupt hits, and dm_crtc_high_irq is the one who answers the door. she handles the CRTC/VSYNC interrupt by notifying DRM's VBLANK event handler. main character energy, honestly. ✨

now for the lore 🧚 — on DCE she's the one on duty (that's VLINE0, set to vblank start). on DCN though? different girl, different path: the equivalent handling is driven by VUPDATE_NO_LOCK in dm_vupdate_high_irq. so like, know which one you're dealing with, bestie. 👑

no guessing, no assuming — the DCE/DCN split above is literally how it works. 💀

---

🎀 SEE ALSO 🎀

kernel file ./drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_irq.c — go read her, she's the source 🌈

and the whole friend group 💖:

• overview(9)
• struct amdgpu_dm_irq_handler_data(9)
• dm_irq_work_func(9)
• amdgpu_dm_irq_register_interrupt(9)
• amdgpu_dm_irq_unregister_interrupt(9)
• amdgpu_dm_irq_init(9)
• amdgpu_dm_irq_fini(9)
• amdgpu_dm_irq_handler(9)
• amdgpu_dm_hpd_init(9)
• amdgpu_dm_hpd_fini(9)
• amdgpu_dm_hdmi_hpd_debounce_work(9)
• dmub_hpd_callback(9)
• dmub_hpd_sense_callback(9)
• dm_pflip_high_irq(9)
• dm_crtc_high_irq_handler(9)
• dm_dcn_vertical_interrupt0_high_irq(9)
• dm_dmub_outbox1_low_irq(9)

---

okay that's the whole page, ily, stan kernel docs 💜🌸✨

signed off with love from ./drivers/gpu/drm/amd/display/... — October 2026, dm_crtc_high_irq(9), periodt. 💅🎀