dm_crtc_high_irq_handler(9)
π NAME π
okay so bestie, this is the dm_crtc_high_irq_handler page from the Kernel API Manual β¨ and its whole vibe is Common OTG vblank/flip event handling π
β¨ SYNOPSIS β¨
it's giving:
void dm_crtc_high_irq_handler (struct amdgpu_device *adev , struct amdgpu_crtc *acrtc );
π ARGUMENTS π
adevβ amdgpu device π«Άacrtcβ the CRTC to service. Performs writeback completion, vblank event handling, CRC processing, VRR BTR updates and pageflip completion delivery. no cap, it's doing a lot π
πΈ DESCRIPTION πΈ
On DCN this is driven by VUPDATE_NO_LOCK (the register latch point) from dm_vupdate_high_irq; on DCE it is driven by VLINE0 at the start of vblank from dm_crtc_high_irq. that's the whole lore β¨
π¦ SEE ALSO π¦
your reading list, bestie:
- Kernel file
./drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_irq.c 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(9)dm_dcn_vertical_interrupt0_high_irq(9)dm_dmub_outbox1_low_irq(9)
mwah π β signing off with the source/version line pointing at ./drivers/gpu/drm/amd/display/... and the date October 2026, from the Kernel API Manual. dm_crtc_high_irq_handler(9) out π
β¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms