drm_connecto...pd_irq_event(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– drm_connecto...pd_irq_event(9) πŸ’–

okay so bestie, we're in the Kernel API Manual today (yes, the Kernel API Manual, the drm_connecto...pd_irq_event(9) one, keep up πŸ’…) and this page is lowkey a little baddie about hotplug processing. let's get into it ✨


🌸 NAME 🌸

drm_connector_helper_hpd_irq_event β€” hotplug processing. that's it, that's the whole vibe 🫢


✨ SYNOPSIS ✨

bool drm_connector_helper_hpd_irq_event (struct drm_connector *connector
);

yes it returns a bool, yes there's exactly one argument, no we're not done yet 😌


πŸŽ€ ARGUMENTS πŸŽ€

  • connector β€” a struct drm_connector, the main character of this whole function fr fr

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea πŸ‘‘ β€” drivers can use this helper function to run a detect cycle on a connector that has the DRM_CONNECTOR_POLL_HPD flag set in its polled member. like, that flag is the invite to the party and this function is the party πŸ’…

this helper is perfect for drivers that can track hotplug interrupts for a single connector β€” one connector, one interrupt, one slay ✨

drivers that want to send a hotplug event for all connectors, or that simply can't track hotplug interrupts per connector, need to use drm_helper_hpd_irq_event instead. different function, different vibe, iykyk 🧚

⚠️ also important: this function must be called from process context with no mode setting locks held. like, none. zero. not even one. this is not a drill 😭

and note πŸ“: a connector can be both polled and probed from the hotplug handler, in case the hotplug interrupt is known to be unreliable. yeah, belt and suspenders energy, we love a backup plan πŸ“


⭐ RETURN ⭐

a boolean indicating whether the connector status changed or not β€” true if it changed, false if it's giving "nothing to see here" πŸ’€


🌈 SEE ALSO 🌈

buckle up bestie, this list is long, but every single one of these is iconic in its own right 🫢


and that's the whole page, no cap πŸ’œ this lil masterpiece lives over in ./drivers/gpu/drm, and it's dated October 2026 β€” so yeah, from the future, obviously πŸ’…βœ¨ see u in the next manpage, mwah πŸŽ€

πŸ“¦ where this page comes from