amdgpu_dm_hd...ebounce_work(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… amdgpu_dm_hdmi_hpd_debounce_work πŸŽ€

okay so bestie, we're in the Kernel API Manual, section 9 β€” yes, the big-girl kernel section, come on in, the water's fine ✨

This one's the HDMI HPD debounce delay, measured in milliseconds. Real talk: when an HDMI display toggles HPD (like, say, during power save transitions β€” you know the vibe 😴), this delay is literally the amount of time the driver waits before it goes and processes that HPD event. It's giving "chill, let me think for a sec" energy 🧚

And why do we care? Because this is how the driver tells apart two very different situations:

  • a physical unplug β€” that's when the toggle is greater than hdmi_hpd_debounce_delay πŸ”ŒπŸ’€
  • a spontaneous RX HPD toggle β€” that's when it's less than hdmi_hpd_debounce_delay πŸŒ€

If the toggle comes in less than this delay, the driver goes ahead and compares the sink capabilities, and it'll permit a hotplug event if they changed. slay. that's the whole check πŸ‘‘

As for the default: it's 1500ms, and no, that number wasn't just picked out of thin air πŸ™ˆ it was chosen based on experimental testing with various monitors that exhibit spontaneous HPD toggling behavior. so like, actual science was done. respect it πŸ’…

✨ SEE ALSO ✨

go check out the kernel file ./drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_irq.c β€” it's the main character of this whole friend group 🫢 and then these icons right here:


okay that's the whole page, mwah πŸ’‹ it came from ./drivers/gpu/drm/amd/display/... and it's dated October 2026 β€” so jot that down, and remember the page name is amdgpu_dm_hd...ebounce_work(9) if you ever gotta cite your sources. bye bestie, go debounce something πŸŒΈπŸ¦‹

πŸ“¦ where this page comes from