dm_test_vbl...worker_setup(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dm_test_vblank_control_worker_setup — from the Kernel API Manual, bestie ✨

okay so real quick before we dive in: this page lives in the Kernel API Manual, and the star of the show is dm_test_vblank_control_worker_setup. say it with me. it's a mouthful but we're gonna slay it 🎀

✨ NAME ✨

dm_test_vblank_control_worker_setup — builds a vblank_control_work for the worker, that's literally the whole job 💖

🌸 SYNOPSIS 🌸

struct vblank_control_work * dm_test_vblank_control_worker_setup (struct
kunit *test , bool enable , uint32_t count );

look at her go 🫶

🦋 ARGUMENTS 🦋

  • test — the KUnit test context. yeah, the whole test vibe lives in here ✨
  • enable — the value that gets dropped into vblank_work->enable. simple as that 💅
  • count — the initial dm->active_vblank_irq_count. like, its starting number, no cap 🔢

👑 DESCRIPTION 👑

so what does she actually do? she returns a work item, and that work item is wired up to a freshly allocated adev/crtc/stream combo — brand new, never been used, main character energy only 🌟

here's the lil detail that matters: the CRTC is left without an atomic state. on purpose. iconic. and because of that, amdgpu_dm_ism_commit_event short-circuits, which means only the vblank IRQ accounting inside the worker actually runs. nothing else. she's focused 💀✨

🔥 SEE ALSO 🔥

📁 Kernel file

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

🧚 the whole friend group (aka every single related page, yes all of them)

like I said. the whole group chat 🌈

ngl this page is short but she's important — dm_test_vblank_control_worker_setup is the setup half of the vblank-control test trio, and her friends are right up there ⬆️

and that's the tea, bestie 🍓 this page came out of ./drivers/gpu/drm/amd/display/... and it's dated October 2026 — so yeah, she's from the future, we stan a forward-thinking icon 💜👑 periodt.

📦 where this page comes from