dm_test_cap...within_limit(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dm_test_cap...within_limit(9) — the Kernel API Manual, but make it cute

okay bestie, so this page lives in the Kernel API Manual under the name dm_test_cap...within_limit(9), and honestly? It's a tiny little test function with a big personality. Let's get into it ✨

🌸 NAME

dm_test_cap_clock_levels_within_limit — the test that proves nothing gets capped when everything's already within the limit. She's a good girl, your honor 🎀

✨ SYNOPSIS

void dm_test_cap_clock_levels_within_limit (struct kunit *test );

That's it. One argument. No drama. Periodt.

🦋 ARGUMENTS

  • test — the KUnit test context. She's the whole vibe check wrapper for this test, mwah 💖

🔥 DESCRIPTION

So the whole point, fr fr: this test verifies that num_levels is left unchanged when no level exceeds the validation clock. Like, everybody's behaving, nobody's over the line, so nothing gets capped — and num_levels stays exactly where it was. No cap. No changes. Just vibes 😌✨

no cap literally. that's the test. the test is "no cap". i'm obsessed 💀

👑 SEE ALSO

okay this is the part where the page goes feral and lists basically every test in the file. grab a snack bestie, we're going in 🍓

The file itself:

  • Kernel file ./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_pp_smu_test.c

Struct + setup:

Default clock levels:

dc_to_pp clock types:

pp_to_dc clock levels:

get_funcs variants:

apply / build helpers:

cap_clock_levels tests (siblings of this one 💜):

nv clock id:

requirements + clock-level lookups:

watermark notifications:

apply_clock_for_voltage trio:

nv display count / voltage / handshake:

rn dpm clock table:

rv set_* crew:

nv set_* crew:

nv sustainable clocks + uclk dpm states:

and one lonely little watermarks test to close it out 🫶:

🧚 sign-off

That's the whole page, bestie! Sourced from ./drivers/gpu/drm/amd/display/... — October 2026, from the Kernel API Manual. Slay, go read your tests, ily, bye 💖✨🎀

📦 where this page comes from