dm_test_repl...ing_dmub_srv(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

dm_test_replay_set_caps_missing_dmub_srv β€” bestie, this one verifies that missing DMUB gets rejected 🫢

So real quick, this is a page from the Kernel API Manual (yes, the kernel has lore too ✨) and it's all about one lil KUnit test that checks the sad path: what happens when Replay is supported but the DMUB service ghosted us πŸ’€


🌸 SYNOPSIS 🌸

void dm_test_replay_set_caps_missing_dmub_srv (struct kunit *test );

That's the whole signature, no cap β€” void in, nothing out, just vibes and a KUnit verdict πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • test β€” the KUnit test context 🧚 this is the lil handle the test framework hands you so the test can do its thing and report back. Basically the group chat the test posts its results in.

✨ DESCRIPTION ✨

Okay so picture it: the link and the connector both support Replay (iconic, love that for them 🌈) but there's no DMUB service available β€” like, nobody's home, the service didn't show up to the party 😭

In that exact situation, amdgpu_dm_set_replay_caps should return false.

That's it. That's the test. It's giving "expect the rejection," and honestly the rejection is the whole point β€” this test is the vibe check that makes sure the code doesn't pretend everything's fine when the DMUB service is literally missing πŸ’…


πŸ¦‹ SEE ALSO πŸ¦‹

The kernel file lives right here, go read the source bestie:

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

And here's the whole friend group of sibling tests β€” every single one, in order, no skips πŸ™ˆ


Okay that's the whole page, mwah πŸ’‹ thanks for reading, this came from ./drivers/gpu/drm/amd/display/... and it's dated October 2026, so mark your calendars bestie β€” see you in the future, dm_test_repl...ing_dmub_srv(9) out πŸŽ€βœ¨

πŸ“¦ where this page comes from