alloc_test_workqueue(9)

📦 version 7.3.1, in nixpkgs unstable

💅 alloc_test_workqueue(9) — bestie edition 🎀

okay so this is a page from the Kernel API Manual, and honestly? it's a little one, but it's important, so let's go ✨

✨ NAME ✨

alloc_test_workqueue — allocate a minimal hdcp_workqueue for testing 🧚

🌸 SYNOPSIS 🌸

struct hdcp_workqueue * alloc_test_workqueue (struct kunit *test );

🦋 ARGUMENTS 🦋

  • test — the KUnit test context, and it's the one doing the managed allocation, so everything gets cleaned up for you. main character energy fr fr 👑

💖 DESCRIPTION 💖

So what this does: it allocates and initialises a minimal hdcp_workqueue — like, just enough of one to be sufficient for process_output testing. That's the vibe. 🫶

And listen, it's not doing the whole thing — only the three delayed works that get accessed by process_output are initialised. Everything else? zeroed. literally zeroed. no cap. 💀

lowkey the whole point: minimal struct, three dworks live, the rest is vibes and zeros ✨

🔥 SEE ALSO 🔥

📁 Kernel file

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

🧚 the hdcp ones

🌈 process_output girlies

⭐ event / property update crew

💜 callback + property validate squad

🎀 watchdog + cpirq

🍓 display enable / disable

👑 create_workqueue things

💅 psp / srm data

✨ locked workqueue + connector

🌈 assr + update_config

and that's the whole page bestie, ike ✅

ok final sign-off: this one's from ./drivers/gpu/drm/amd/display/... and it's dated October 2026, part of the Kernel API Manual, and it's literally called alloc_test_workqueue(9). slay. 💖🎀✨
📦 where this page comes from