dm_test_crtc...nk_full_path(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

dm_test_crtc_enable_vblank_full_path β€” this test is literally about checking that the enable path runs to completion. That’s the whole assignment, bestie. πŸ’…

okay so this page is dm_test_crtc...nk_full_path(9) from the Kernel API Manual, and the actual function name is the full one up there β€” she’s the main character of this page. πŸŽ€


🌸 SYNOPSIS 🌸

void dm_test_crtc_enable_vblank_full_path (struct kunit *test );

that’s the signature, character for character β€” no edits, no β€œfixing,” periodt. ✨


πŸ’– ARGUMENTS πŸ’–

  • test β€” the KUnit test context. that’s all she wrote.

πŸ”₯ DESCRIPTION πŸ”₯

okay so picture this: there’s a configured CRTC on a VRR-capable DC, and both the crtc/pageflip IRQ sources are armed. In that setup, the enable path walks the vupdate-irq branch β€” because VRR is active and OTG is unassigned, so it returns early there. Along the way it acquires both IRQ references and completes with no vblank workqueue queued. that’s the whole vibe check, and the test is confirming the enable path runs all the way to completion. πŸ¦‹


πŸ‘€ SEE ALSO πŸ‘€

  • Kernel file: ./drivers/gpu/drm/amd/display/amdgpu_dm/tests/amdgpu_dm_crtc_test.c

and now the whole test squad, bestie β€” every single one, in order:

cute sign-off: the footer says source/version ./drivers/gpu/drm/amd/display/... and October 2026, with page tag dm_test_crtc...nk_full_path(9) β€” mwah, bye bestie πŸ’‹πŸŽ€βœ¨

πŸ“¦ where this page comes from