dm_test_rep...eady_enabled(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the Kernel API Manual πŸ’– this one's a KUnit test function and honestly it's giving "small but mighty" β€” let's get into it ✨


✨ NAME ✨

dm_test_replay_link_setup_already_enabled β€” the vibe check that makes sure Replay succeeds when it's already enabled πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

void dm_test_replay_link_setup_already_enabled(struct kunit *test);

πŸ’… ARGUMENTS πŸ’…

  • test β€” the KUnit test context 🧚 that's it, that's the whole argument, it's carrying the whole test on its back fr fr

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the situation, bestie πŸ’œ when Replay is already enabled, amdgpu_dm_link_setup_replay should return true β€” and the whole point of this test is to confirm it does exactly that without recalculating coasting vtotal state 🫢 like, no re-deriving, no extra math, just vibes and a clean true. periodt πŸ’…


🌈 SEE ALSO 🌈

the whole friend group 🫢 literally the entire replay test squad, go say hi:


ngl this page is a little truncated in the corner β€” the header shows up as dm_test_rep...eady_enabled(9) and the footer's source line as ./drivers/gpu/drm/amd/display/... β€” but the ✨ full function name ✨ is dm_test_replay_link_setup_already_enabled, iykyk 😭

okay and finally the cute lil sign-off πŸŽ€ this page is from October 2026, lives in the Kernel API Manual, and it says bye as dm_test_rep...eady_enabled(9) β€” mwah, slay, go read the source file, ily, bye bestie πŸ’–πŸ¦‹βœ¨

πŸ“¦ where this page comes from