dm_test_eve...atchdog_idle(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dm_test_event_cpirq_leaves_callback_and_watchdog_idle(9) πŸ’…

okay bestie, this is a Kernel API Manual page, section 9, and the full title of this whole thing is dm_test_event_cpirq_leaves_callback_and_watchdog_idle β€” yes it's a mouthful, yes the header hugs it down to dm_test_eve...atchdog_idle(9), we don't have infinite screen width okay 😭


✨ NAME ✨

dm_test_event_cpirq_leaves_callback_and_watchdog_idle β€” the test whose whole personality is only validate is queued. That's it. That's the vibe check. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

void dm_test_event_cpirq_leaves_callback_and_watchdog_idle (struct kunit
*test );

🌸 ARGUMENTS 🌸

  • test β€” the KUnit test context 🧚 she's the main character, everybody else is just visiting.

πŸ”₯ DESCRIPTION πŸ”₯

So picture it: there's no active hdcp display. None. Zero. Ghost town 🫢

In that situation, mod_hdcp_process_event leaves the output cleared. And because the output is cleared, event_cpirq must not schedule callback_dwork and must not schedule watchdog_timer_dwork. Like, not even a little. Not on her watch πŸ’€

The only thing that gets enqueued is property_validate_dwork. Just the one. That's the entire test. That's the whole point. Periodt. πŸ‘‘


⭐ SEE ALSO ⭐

so here's the friend group β€” the Kernel file this lives in, plus literally everyone adjacent, no cap:

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


and that's the page!! πŸ’– little sign-off moment: this one comes from ./drivers/gpu/drm/amd/display/... (yes, truncated, she's mysterious 🌈) and it's dated October 2026 β€” bookmark it, screenshot it, put it on your fridge πŸ“βœ¨

πŸ“¦ where this page comes from