drm_sysfs_co...operty_event(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_sysfs_connector_property_event(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” this one's a little function with a big name and honestly it's giving "I only do one thing but I do it iconically." Let's get into it ✨


πŸŽ€ NAME πŸŽ€

drm_sysfs_connector_property_event β€” the function that generates a DRM uevent whenever a connector property changes. that's it, that's the whole vibe. lowkey essential, fr fr πŸ¦‹


🌸 SYNOPSIS 🌸

void drm_sysfs_connector_property_event (struct drm_connector *connector
, struct drm_property *property );

she takes two pointers and returns absolutely nothing (void, queen of not overcommitting πŸ’…). copy it exactly like that, spacing and all β€” do not come for her formatting.


🧚 ARGUMENTS 🧚

  • connector β€” the connector whose property just changed. like, the actual connector. the one having a moment. 🫢
  • property β€” the connector property that changed. this is the thing that decided to be different. πŸ™ˆ

πŸ”₯ DESCRIPTION πŸ”₯

the whole job, in one breath: send a uevent for the specified DRM connector and property. ✨

and like, what actually goes in that uevent? currently we set HOTPLUG=1 plus the connector id, along with the attached property id related to the change. that's the payload, no cap. πŸŽ€

so if you were wondering "does this thing just yell into the void?" β€” no bestie, it yells into the void with structured data. main character energy honestly πŸ‘‘


🌈 SEE ALSO 🌈

the friend group, if you will β€” go say hi to all of them:


heads up bestie: the title up there got cut off in the original page as drm_sysfs_co...operty_event(9) β€” that's just how it's printed, not me being lazy πŸ’€

⭐ that's a wrap! this page lives in ./drivers/gpu/drm and it's stamped October 2026 β€” so yeah, she's from the future, obsessed. periodt. πŸ’–πŸŒΈπŸ¦‹πŸŽ€

πŸ“¦ where this page comes from