drm_connect...otplug_event(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– drm_connector_oob_hotplug_event(9) πŸ’–

okay bestie, welcome to the Kernel API Manual, grab a boba and let's get into it ✨ this one is short, sweet, and honestly kinda iconic for what it does.


🌸 NAME 🌸

drm_connector_oob_hotplug_event β€” report an out-of-band hotplug event to a connector πŸ¦‹

like, something got plugged in and the usual path didn't hear about it, so we're telling the connector directly. no cap.


✨ SYNOPSIS ✨

void drm_connector_oob_hotplug_event (struct fwnode_handle
*connector_fwnode , enum drm_connector_status status );

void function, two args, that's the whole vibe πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • connector_fwnode β€” the fwnode_handle you're reporting the event on πŸ‘‘ this is your "who is this about" arg.
  • status β€” the hot plug detect logical state 🌈 basically "hey, here's the state we detected."

πŸ’œ DESCRIPTION πŸ’œ

so on some hardware, a hotplug event notification can come from outside the display driver / device. literally from elsewhere. main character energy, honestly.

an example of this? some USB Type-C setups, where the hardware muxes the DisplayPort data and aux-lines but does not pass the altmode HPD status bit to the GPU's DP HPD pin 😭 the GPU is sitting there like "??" and nobody tells it anything.

this function is how you fix that. use it to report these out-of-band events β€” but key detail, bestie: you do it after obtaining a drm_connector reference through calling drm_connector_find_by_fwnode. ✨ so find the connector first, then report. in that order. fr fr.

🫢 read that again if you need to β€” reference first via drm_connector_find_by_fwnode, then report the event. don't skip the find step, i'm begging.

πŸ”₯ SEE ALSO πŸ”₯

okay this list is a whole journey, buckle up 🧚 every single one of these is here:

πŸ’€ yes, standard connector properties(9) shows up twice in the list. twice! we love a duplicate, she's consistent, we keep her both times. periodt.

and that's the whole page, bestie πŸ“ this one lives over in ./drivers/gpu/drm, dated October 2026 πŸ’– go report those out-of-band events and slay πŸ’…βœ¨

πŸ“¦ where this page comes from