drm_sysfs_c...otplug_event(9)

👑 drm_sysfs_connector_hotplug_event — the Kernel API Manual page you didn't know you needed 💅

okay so bestie, welcome to the Kernel API Manual, section 9 (iykyk, that's the kernel-functions section 🧚). The page header is literally drm_sysfs_c...otplug_event(9) because even the manpage generator got distracted halfway through typing, and honestly? relatable. Anyway, we're talking about drm_sysfs_connector_hotplug_event and she is the girl who tells the world your connector changed. 🦋

---

✨ NAME ✨

drm_sysfs_connector_hotplug_event — generate a DRM uevent for any connector change 🌸

like, any change. any connector. she's not picky, she's just the messenger. 🎀

✨ SYNOPSIS ✨

void drm_sysfs_connector_hotplug_event (struct drm_connector *connector);

one function, one argument, returns void — she gives nothing back emotionally but she does the work. 😭

✨ ARGUMENTS ✨

• _connector_ — the struct drm_connector that has changed. that's it. that's the whole thing. she just wants to know which connector is having a moment. 💖

✨ DESCRIPTION ✨

so here's the tea 🍓: this function sends a uevent for the DRM connector specified by _connector_. that's the whole vibe.

and not just any uevent, bestie — she ships it with the properties HOTPLUG=1 and CONNECTOR. those two are non-negotiable, they're the whole point, they're the main character energy of this function. 👑

one function call and the whole userspace knows something moved. no cap. 🔥

✨ SEE ALSO ✨

the friend group 🫶 — go read these next, fr fr:

• Kernel file ./drivers/gpu/drm/drm_sysfs.c overview(9)
• drm_sysfs_init(9)
• drm_sysfs_destroy(9)
• drm_sysfs_hotplug_event(9)
• drm_sysfs_connector_property_event(9)
• drm_class_device_register(9)
• drm_class_device_unregister(9)

---

and that's the page, bestie 💜 this little beauty lives over in ./drivers/gpu/drm, dated October 2026, and it's brought to you by the Kernel API Manual. slay, go hotplug something. ✨🎀💅