dm_test_crtc...ive_disabled(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so this is dm_test_crtc_vrr_active_disabled(9) — a page straight out of the Kernel API Manual, section 9, bestie 💅

and what does it actually do? it tests Crtc vrr active disabled ✨ that's the whole vibe. it's a KUnit test, it checks the thing, it slays.

🎀 SYNOPSIS 🎀

void dm_test_crtc_vrr_active_disabled (struct kunit *test );

that's literally it. one function, no return value (void, so it gives you nothing back and honestly same), takes one arg. no cap 🫶

🦋 ARGUMENTS 🦋

  • test — the KUnit test context 💖 this is the little container the test framework hands you so the test knows where it lives and can report stuff back to the harness. it's giving "here's your paperwork, go do your thing" ✨

👑 SEE ALSO 👑

🍓 bestie there are so many siblings. like, this test has a whole extended family. every single one is listed below, exactly as-is, no edits, no cap:

Kernel file — ./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_crtc_test.c 🔥

the crtc-adjacent crew on the modeset-required side:

the vrr-active irq squad 🌈:

the vrr-active originals (aka our people) 💜:

the is_headless lineup 🎀:

helpers, vupdate irqs, and the idle workers 🧚:

static screen optimize (yes it's spelled optimze in the source, we do not fix it, that's iconic behavior) ⭐:

the enable_vblank gang 💀:

active planes counting 🔥:

state duplication / reset / destroy, the holy trinity of "please don't leak, please don't leak" 🙈:

vblank handling, where the drama happens 😭:

vblank control worker, doing worker things 🫶:

and finally the disable_vblank trio, going out on a high note 💖:

and that's the whole page, bestie 🦋✨

this little icon came from ./drivers/gpu/drm/amd/display/... and the version stamp is dated October 2026, so like… future-core of it all 💅 mwah, go write some KUnit tests, ily 🎀

📦 where this page comes from