dm_test_crtc...eases_stream(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dm_test_crtc_destroy_state_releases_stream 💅

okay so this is a page straight out of the Kernel API Manual, and it's about one specific KUnit test — yes, that one. buckle up bestie 🎀

✨ NAME ✨

dm_test_crtc_destroy_state_releases_stream — the test that checks destroying the state actually releases the stream. no cap, that's the whole gig 🫶

🌸 SYNOPSIS 🌸

void dm_test_crtc_destroy_state_releases_stream(struct kunit *test);

🦋 ARGUMENTS 🦋

  • test — the KUnit test context 💖 literally just the test's own little context handle, that's it, that's the whole argument.

🔥 DESCRIPTION 🔥

okay so picture this: the CRTC state is out here carrying a DC stream, right? and the rule is, when you destroy that state, it must release a stream reference. non-negotiable. it's giving basic hygiene honestly 💅

here's the cute part though — the test takes an extra reference up front. why? because then when the release happens, it just drops that extra one and the KUnit-managed reference stays intact. so instead of the stream getting freed right here in the middle of the test (which would be a whole mess 😭), everything stays chill and the test can keep doing its thing. slay.

ngl this is a test, so it's for the kernel devs, not for you to run on your laptop at 3am. but the logic is iconic and that's what matters ✨

👑 SEE ALSO 👑

bestie there are like a lot of siblings in this family, so let's go. the kernel file lives here:

./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_crtc_test.c

and here's the whole crew, no one left out fr fr 💜

that's the whole page babes, every single cross-reference accounted for, nothing dropped 💖

and for the cute sign-off: this one comes to you from ./drivers/gpu/drm/amd/display/... and it's dated October 2026 — so like, future vibes only ⭐🦋 see you in the next manpage bestie 🫶💅

📦 where this page comes from