amdgpu_dm_c...te_writeback(9)

💅 amdgpu_dm_crtc_complete_writeback — the Kernel API Manual, bestie edition 🎀

okay so this page lives in the Kernel API Manual and it's all about amdgpu_dm_crtc_complete_writeback (the header truncates it as amdgpu_dm_c...te_writeback(9), which is giving "name too long for the terminal, we simply must abbreviate" 😭). It's a tiny little function that closes out a writeback job, and honestly? It ate. Let's get into it ✨

---

🌸 NAME 🌸

amdgpu_dm_crtc_complete_writeback — literally just finishing up a pending writeback job 🫶

---

🦋 SYNOPSIS 🦋

bool amdgpu_dm_crtc_complete_writeback (struct amdgpu_crtc *acrtc );

she takes one pointer and she returns a bool. that's the whole vibe check 💅

---

🌈 ARGUMENTS 🌈

• acrtc — the CRTC whose pending writeback should be completed, i.e. the main character of this whole operation 👑

---

💖 DESCRIPTION 💖

So here's what she does: she clears the pending state, she signals the writeback out fence, and she releases the vblank reference that was taken back in dm_set_writeback while the writeback was armed. Cleanup queen behavior, no notes 🔥

Now the important part, bestie, because this is the ✨iconic✨ bit: the pending flag is tested and cleared under the writeback job lock. Which means it is safe to call concurrently from the completion vblank IRQ (dm_crtc_high_irq) and from the writeback teardown path (dm_clear_writeback). Two callers, one lock, zero drama 🙈

And the rule? Only the caller that observes the pending job performs the completion. So it's like — first one in the group chat gets to reply, everyone after that just reads it. periodt 💀

ngl this is a "one of you does the work, the rest of you relax" situation — the lock is what makes it true, so don't go thinking you can skip it 🎀

---

⭐ RETURN ⭐

true if a pending writeback job was completed by this call. That's it. That's the whole answer — no false footnote needed, when it's true it's true 💜

---

🍓 SEE ALSO 🍓

Kernel file ./drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c — because we always cite our sources, iykyk 📚

• overview(9)
• update_planes_and_stream_adapter(9)
• dm_hw_init(9)
• dm_hw_fini(9)
• amdgpu_dm_dump_links_and_sinks(9)
• DM Lifecycle(9)
• atomic(9)
• fill_dc_dirty_rects(9)
• dm_arm_vblank_event_pre_programming(9)
• amdgpu_dm_mod_power_update_streams(9)
• amdgpu_dm_mod_power_setup_streams(9)
• amdgpu_dm_atomic_commit_tail(9)
• amdgpu_dm_atomic_check(9)

---

okay that's the page!! mwah 💋 this one came from ./drivers/gpu/drm/amd/display/... and it's dated October 2026, so mark your calendars bestie 🗓️✨ and yeah, the footer still insists on calling it amdgpu_dm_c...te_writeback(9) — we let her have that one 🌸🫶💅