dmub_hw_lock...require_lock(9)
β¨ dmub_hw_lock...require_lock(9) β¨
okay bestie, welcome to the Kernel API Manual page for dmub_hw_lock...require_lock(9) π β yes that's the real title, no I didn't make it up, and yes it's a mouthful. buckle up, this one's short but she's important. π
πΈ NAME πΈ
dmub_hw_lock_mgr_does_context_require_lock β literally returns true if the context has any stream that needs the HW lock. that's it. that's the whole job. and she does it flawlessly. π
π¦ SYNOPSIS π¦
bool dmub_hw_lock_mgr_does_context_require_lock (const struct dc *dc ,
const struct dc_state *context );
not me copy-pasting this exactly because the vibes may change but the signatures never do, fr fr π
π ARGUMENTS π
dcβ Pointer to the DC object. just pointing at it. being a whole DC object about it. π«Άcontextβ The context to check. yes queen, we're checking you. π
β RETURN β
true if the context has any stream that needs the HW lock, false otherwise β¨ β a clean little boolean, no cap, no surprises, exactly as iconic as it sounds. π
π SEE ALSO π
- 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_link_require_lock(9)should_use_dmub_inbox0_lock_for_link(9)
she runs with a whole squad, and every single one of them is listed above, character for character. π§
lowkey a reminder: everything above is exactly what the page says β the flags, the paths, the section names β just with way better energy. don't come at me with "you changed something," because I did not. π
and that's the page!! mwah π this lil gem lives at ./drivers/gpu/drm/amd/display/..., dated October 2026, and it's part of the Kernel API Manual, section 9. periodt. πΈππ¦
π¦ 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