drm_atomic_...or_connector(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_atomic_set_crtc_for_connector β€” set CRTC for connector

okay so this is a page from the Kernel API Manual (yes, the Kernel API Manual, we're in that part of the docs bestie, the GPU driver section) and honestly? it's a little baddie with one job and she does it πŸ’–


✨ SYNOPSIS ✨

int drm_atomic_set_crtc_for_connector (struct drm_connector_state
*conn_state , struct drm_crtc *crtc );

like, yes, that's the whole signature, no cap 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • conn_state β€” the atomic state object for the connector. that's her little state era πŸ’…
  • crtc β€” the CRTC to use for the connector. the actual destination, the main character πŸ‘‘

🌸 DESCRIPTION 🌸

so when you're changing the assigned CRTC for a connector, you can't just do it, babes, because you need to grab the lock and the state for the new CRTC as needed 😭 like there are steps.

this function takes care of all those details 🫢

the one thing she does not do? updating the pointer in the state object itself. nope, that part's on you, bestie. she handles the logistics, you handle the pointer, it's giving teamwork πŸ’–


⭐ RETURN ⭐

  • 0 β€” success, slay, we ate πŸŽ‰
  • -EDEADLK β€” uh oh. when the error is EDEADLK that means the w/w mutex code has detected a deadlock, and the entire atomic sequence must be restarted πŸ” like, the whole thing, from the top, no skipping πŸ™ˆ
  • -ENOMEM β€” out of memory, tragic πŸ’€
also: all other errors are fatal. like, genuinely, not in a cute way. periodt.

πŸ¦‹ SEE ALSO πŸ¦‹

the girlies in her orbit πŸ’«


🌈 the sign-off 🌈

okay that's the whole page, ily, go set some CRTCs responsibly πŸ’œ

this little beauty comes from ./drivers/gpu/drm, and the page is dated October 2026, filed under drm_atomic_...or_connector(9) β€” yes the truncated title is literally part of the vibe, don't come for her πŸŽ€

πŸ“¦ where this page comes from