should_use_dmub_inbox1_lock(9)

✨ should_use_dmub_inbox1_lock(9) ✨

okay so bestie, welcome to the Kernel API Manual for should_use_dmub_inbox1_lock — section 9, kernel devs only, very "i know what this header file does and you don't" energy. let's get into it 💅

---

🌸 NAME 🌸

should_use_dmub_inbox1_lock — literally just checks if the DMCUB hardware lock via inbox1 should be used. that's the whole vibe check. yes/no. iconic.

---

🎀 SYNOPSIS 🎀

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

it returns a bool, it takes a dc and a link, and no, you cannot skip the arguments. i know, i know. 😭

---

💖 ARGUMENTS 💖

• dc — pointer to the DC object 🫶 like, the whole display core thing, you gotta hand it over
• link — optional pointer to the link object, used to check for enabled link features ✨ optional!! so you can pass something else, but if you're passing a link, this is how it peeks at which features are turned on

---

🔥 RETURN 🔥

it gives you back true if the inbox1 lock should be used, and false otherwise. that's it. that's the tea. ☕ no cap.

---

💜 SEE ALSO 💜

• the kernel file ./drivers/gpu/drm/amd/display/dc/dce/dmub_hw_lock_mgr.h — go read it, it's giving source of truth 🧚
• dmub_hw_lock_mgr_does_link_require_lock(9)
• dmub_hw_lock_mgr_does_context_require_lock(9)
• should_use_dmub_inbox0_lock_for_link(9) — yes, inbox0, the sibling. not the same thing, don't get it twisted 💀

---

ngl this whole page is like four lines of actual info and honestly? respect. short and slays. 🦋

---

okay that's the whole page, bestie 🌈 — big kisses from ./drivers/gpu/drm/amd/display/..., dated October 2026, filed under should_use_dmub_inbox1_lock(9) in your fave Kernel API Manual. go forth and lock that inbox1 💖👑