intel_hpd_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… intel_hpd_init β€” the Kernel API Manual page, bestie edition ✨

okay so real talk, this one's from the Kernel API Manual, section 9, and it's called intel_hpd_init πŸ’–


🌸 NAME 🌸

intel_hpd_init β€” literally initializes and enables hpd support, that's the whole job, no cap ✨


πŸŽ€ SYNOPSIS πŸŽ€

void intel_hpd_init(struct intel_display *display);

πŸ¦‹ ARGUMENTS πŸ¦‹

  • display β€” the display device instance 🫢 that's your one and only input, she's low maintenance

πŸ‘‘ DESCRIPTION πŸ‘‘

okay so here's the tea β˜• this function enables the hotplug support. slay.

But β€” and this is important, bestie β€” it requires that interrupts have already been enabled with intel_irq_init_hw. like, do that first, okay? order matters, periodt πŸ’…

From this point on, hotplug and poll request can run concurrently to other code, so the locking rules must be obeyed. fr fr, don't skip the locking rules, that's how you get the bad kind of chaos 😭


So why is this its own separate step from interrupt enabling? because it simplifies the locking rules in the driver load and resume code β€” iconic design choice honestly, main character energy 🧚


Also see: intel_hpd_poll_enable and intel_hpd_poll_disable πŸ’œ go read those too, iykyk


🌈 SEE ALSO 🌈

that's a whole friend group right there, obsessed πŸ“


quick vibe check reminder: hotplug + poll requests can run concurrently with other code once this is called, so obey the locking rules or risk undefined chaos πŸ’€

and that's the page, bestie πŸŽ€ this lil gem lives in ./drivers/gpu/drm/i915/display, and it's dated October 2026 β€” so mark your calendar, kiss the screen, and go enable those interrupts first πŸ’–βœ¨πŸ‘‘

πŸ“¦ where this page comes from