drm_connecto...tus_property(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the Kernel API Manual β€” yes that's the manual name, no I'm not making it up πŸ’… this is a (9) page, kernel-API territory, and we're gonna get through it together, hand in hand, no cap 🫢


🌸 NAME 🌸

drm_connector_set_link_status_property β€” sets the link status property of a connector, fr fr


πŸŽ€ SYNOPSIS πŸŽ€

void drm_connector_set_link_status_property (struct drm_connector
*connector , uint64_t link_status );

like, that's the whole signature. she's cute, she's void, she takes two things πŸ’–


πŸ¦‹ ARGUMENTS πŸ¦‹

  • connector β€” the drm connector in question. the main character, honestly πŸ‘‘
  • link_status β€” the new value of the link status property, and listen: 0 means Good, 1 means Bad. that's it, that's the whole scale, binary icon behavior 😭

⭐ DESCRIPTION ⭐

so in the usual working scenario β€” the happy path, the slay path β€” this link status property is always set to "GOOD" ✨

but if something fails during or after a mode set, the kernel driver may set this link status property to "BAD" πŸ’€ and then? the caller needs to send a hotplug uevent so userspace goes and re-checks the valid modes through GET_CONNECTOR_IOCTL and retries the modeset. like a lil "hey bestie something changed, come look" πŸ“£


πŸ™ˆ NOTE πŸ™ˆ

drivers cannot rely on userspace to support this property and issue a modeset. nope, not a thing. so drivers may choose to handle issues themselves β€” like re-training a link β€” without userspace's intervention at all. independent queen energy πŸ’…

the reason this property exists is to handle link training failures, but it is not limited to DP or link training. for example β€” and this is the fun part β€” if we implement asynchronous setcrtc, this property can be used to report any failures in that too 🌈

lowkey important: this thing is not just a DP link-training accessory, it's a general "something went sideways" flag. iykyk.

πŸ”₯ SEE ALSO πŸ”₯

okay this list is long long, so buckle up, we're going through every single one because I don't skip, ever πŸ’œ

yes, standard connector properties(9) shows up twice. I didn't merge them, I didn't "fix" them, I listed them exactly like the original said. leave her alone πŸ“

πŸ’« sign-off πŸ’«

this little gem lives in ./drivers/gpu/drm, dated October 2026, page name drm_connecto...tus_property(9) (the truncation is canon, don't @ me 😭). go forth, set your link status, send your uevents, and remember: 0 is Good, 1 is Bad, and you're doing amazing πŸ§šπŸ’–

πŸ“¦ where this page comes from