dmub_hw_loc...require_lock(9)

✨ dmub_hw_lock_mgr_does_link_require_lock — the vibe check for HW locks ✨

okay so real talk, this one lives in the Kernel API Manual, section 9, and it's literally just one tiny function that answers one tiny question: does this link need the hardware lock or not? that's it. that's the whole gig. 💅

---

🌸 NAME 🌸

dmub_hw_lock_mgr_does_link_require_lock — returns true if the link has a feature that needs the HW lock 🫶

like, it's giving "am I invited to the lock party" but for display links. no cap.

---

🎀 SYNOPSIS 🎀

bool dmub_hw_lock_mgr_does_link_require_lock (const struct dc *dc ,
       const struct dc_link *link );

so you hand it a dc and a link, and it hands you back a bool. iconic behavior fr fr ✨

---

💖 ARGUMENTS 💖

• dc — pointer to the DC object. yes bestie, the whole display core, the main character 👑
• link — the link you wanna check. the one under the microscope 🔍

---

🦋 RETURN 🦋

true if the link has a feature that needs the HW lock, false otherwise 💀

that's it. boolean. binary. two moods. no in-between. 🌈

---

👑 SEE ALSO 👑

• the kernel file ./drivers/gpu/drm/amd/display/dc/dce/dmub_hw_lock_mgr.h — go read it, iykyk 📖
• should_use_dmub_inbox1_lock(9)
• dmub_hw_lock_mgr_does_context_require_lock(9)
• should_use_dmub_inbox0_lock_for_link(9)

the whole lock-manager friend group honestly 🫶

---

heads up bestie: all the actual facts up there are load-bearing. the vibe is mine, the behavior is not. don't go inventing semantics, mwah 💋

---

and that's the page!! source/version lives at ./drivers/gpu/drm/amd/display/..., dated October 2026, filed under dmub_hw_loc...require_lock(9) — stan a tiny kernel helper, periodt 🎀✨💜