dm_test_han...nce_schedule(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dm_test_han...nce_schedule(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual page for dm_test_handle_hpd_irq_helper_debounce_schedule. It’s giving very specific KUnit test energy, and honestly? iconic. Let’s go 🫢


🌸 NAME 🌸

dm_test_handle_hpd_irq_helper_debounce_schedule β€” Test HDMI debounce branch. That’s the whole plot, no cap.

✨ SYNOPSIS ✨

void dm_test_handle_hpd_irq_helper_debounce_schedule (struct kunit *test
);

πŸŽ€ ARGUMENTS πŸŽ€

  • test β€” The KUnit test context. Like, the little test bubble this function lives in πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so picture this: an HDMI link is reporting a disconnect β€” that’s connection type none β€” and there’s a non-zero debounce delay plus a cached local_sink. This test is checking that the code absolutely must take the debounce branch: the way that it caches local_sink in hdmi_prev_sink and schedules the delayed debounce work instead of detecting immediately. That’s the vibe check, and this test is obsessed with making sure it passes, fr fr.

πŸ‘‘ SEE ALSO πŸ‘‘

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

and the whole test-suite group chat:


Signing off with the source/version: ./drivers/gpu/drm/amd/display/... Β· date: October 2026 Β· page: dm_test_han...nce_schedule(9) πŸ’–βœ¨πŸ«Ά

πŸ“¦ where this page comes from