hwss_wait_fo...ank_complete(9)

💖 hwss_wait_fo...ank_complete(9) 💖

okay so real talk, bestie — this page is from the Kernel API Manual (yes, that Kernel API Manual, the one that shows up looking like a cryptic text from the universe), and the function name got a lil' truncated in the header because it's long. The full thing is hwss_wait_for_all_blank_complete, so don't @ me if the title looks like it fainted mid-word 💀.

---

✨ NAME ✨

hwss_wait_for_all_blank_complete — wait for all active OPPs to finish their pending blank pattern updates, no cap 🫶

Like, it literally just sits there and waits. That's the whole vibe. Very patient main character energy.

---

🌸 SYNOPSIS 🌸

void hwss_wait_for_all_blank_complete (struct dc *dc , struct dc_state *context );

Returns void, so it gives you nothing back — it just does the waiting and dips. Ghosting, but make it kernel API 💅

---

🎀 ARGUMENTS 🎀

• dc — [in] dc reference. Yeah, it's a struct dc *, the display core situation, you know the one ✨
• context — [in] hardware context in use. That's your struct dc_state *, the hardware state that's currently living its truth 🌈

Both of these are [in] only, so nothing's getting written back to you. Inputs only, icon behaviour honestly 👑

---

🦋 SEE ALSO 🦋

Kernel file ./drivers/gpu/drm/amd/display/dc/core/dc_hw_sequencer.c — that's where this whole situation lives, go read the source if you're feeling feral 🙈

---

lowkey a heads up: the docs don't tell us anything about return values, error codes, or blocking behaviour beyond "waits for pending blank pattern updates to finish" — so don't go inventing lore, bestie. We report, we don't speculate 🔥

---

and that's the whole page!! mwah 💋 this came from the kernel docs, source path ./drivers/gpu/drm/amd/display/..., dated October 2026 — periodt, go forth and wait responsibly 🧚‍♀️⭐