DALSMC_MSG_SetHardMinByFreq(9)

📦 version 7.3.1, in nixpkgs unstable

💅 DALSMC_MSG_SetHardMinByFreq(9) 💅

okay so this is a page straight outta the Kernel API Manual bestie, and we're talking about DALSMC_MSG_SetHardMinByFreq — yes that's the whole name, it's giving "my parents gave me all my names at once" energy 💀

✨ NAME ✨

DALSMC_MSG_SetHardMinByFreq — sets a lower bound frequency constraint on a PPCLK. That's it, that's the whole vibe: a floor, not a ceiling 🌸

🦋 SYNOPSIS 🦋

DALSMC_MSG_SetHardMinByFreq

no arguments listed up here, the message just exists and does its thing ✨

🎀 DESCRIPTION 🎀

okay so hear me out, this is the important part 👑 the response does NOT indicate that the effective clock has already been raised to meet the minimum requirement. like, it's not gonna tell you "yep bestie we're at frequency now" — nope 🙈 so if you actually want the status of your request, you gotta poll DALSMC_MSG_ReturnHardMinStatus. fr fr, don't assume, poll it 💅

Supported clocks: SOCCLK, DISPCLK, DPPCLK, DCFCLK, DTBCLK — those five, and that's the list, no cap 🫶

Request:

  • FreqKhz[23:0] — the target minimum frequency in kHz, and the range is 0 to ~16.7 GHz 🌈 (yes, kilohertz field with a gigahertz range, that's just how she is 💀)
  • Ppclk[31:24] — the PPCLK_e clock identifier, so it knows which clock we're talking about 🕵️‍♀️

Response: (none beyond result code) — literally nothing else, just the result code and vibes ⭐

lowkey reminder: no response field tells you the clock actually got there. poll DALSMC_MSG_ReturnHardMinStatus or you're just guessing 🙈

🧚 SEE ALSO 🧚

Kernel file ./drivers/gpu/drm/amd/display/dc/clk_mgr/dcn60/dalsmc.h — that's where she lives 🏠

and the whole friend group 👯‍♀️:

🍓 source sitch: ./drivers/gpu/drm/amd/display/... — dated October 2026 ✨ and yes DALSMC_MSG_SetHardMinByFreq(9) again at the end because the manpage said its own name twice and honestly? main character energy 💅 periodt 🎀
📦 where this page comes from