dm_test_link...y_coordinate(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so picture this: you're deep in the kernel, you're vibe-checking PSRSU link support, and the one thing that can ruin the whole party is a missing Y coordinate. this page is literally about that test. it's giving "one job, and it's checking you did it" energy. ✨


🌸 NAME 🌸

dm_test_link_supports_psrsu_missing_y_coordinate β€” Y coordinate support is required, no cap. that's the whole plot. πŸŽ€


✨ SYNOPSIS ✨

void dm_test_link_supports_psrsu_missing_y_coordinate(struct kunit *test);

return type void, so like… don't @ her expecting a value back, she's not giving you one. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • test β€” the KUnit test context. that's it. that's the whole argument list. she travels light. 🫢

🌈 SEE ALSO 🌈

πŸ’œ Kernel file

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

that's where the whole squad lives, bestie. go say hi. πŸ‘‘

πŸ”₯ The rest of the PSR test crew, fr fr

like, that's a full group chat right there. every single one of them got an invite. πŸ’Œ


ngl, the moral of this page is dead simple: if you're claiming PSRSU link support, the Y coordinate better be there. the test name says it, the manpage says it, I'm saying it. 😭

and that's the whole read, bestie! sourced from ./drivers/gpu/drm/amd/display/... β€” dated October 2026 β€” and yeah, the title bar keeps going back to dm_test_link...y_coordinate(9) because it's iconic and refuses to be abbreviated differently. mwah, ily, go check those Y coordinates πŸ’–πŸ¦‹πŸ“

πŸ“¦ where this page comes from