drm_atomic_g...nector_state(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_atomic_g...nector_state(9) — like, the Kernel API Manual bestie ✨

okay so real talk, this one lives in the Kernel API Manual and its whole name got squished by the terminal into drm_atomic_g...nector_state(9) — tragic, I know, but the vibe is immaculate. Let's get into it 🎀

🌸 NAME 🌸

drm_atomic_get_connector_state — get connector state. literally that's the whole thing, short and slay 💖

✨ SYNOPSIS ✨

struct drm_connector_state * drm_atomic_get_connector_state (struct
drm_atomic_commit *state , struct drm_connector *connector );

look at her go 😭🫶

🦋 ARGUMENTS 🦋

  • state — the global atomic state object. yes bestie, the whole big picture 👑
  • connector — the connector you want the state object for. this is your girl 🎀

💜 DESCRIPTION 💜

So this function returns the connector state for the given connector, and it'll allocate it if needed — no cap, it just handles that for you 🫶 It will also grab the relevant connector lock to make sure that the state is consistent. iconic behaviour, honestly, protecting us from our own chaos 💅✨

🌈 RETURN 🌈

You get either the allocated state, or the error code encoded into the pointer. Yes — into the pointer. iykyk 😭

⚠️ okay this part matters, listen up: 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. start over. 💀

All other errors are fatal. like, actually fatal. no reshoots 🙈

🔥 SEE ALSO 🔥

that's a whole friend group right there, we love a linked list of besties 😭💖

and that's the whole page, bestie 🧚✨ this one's filed under ./drivers/gpu/drm, dated October 2026, and it goes by drm_atomic_g...nector_state(9) — mwah, go read some more manpages, ily 🫶🍓

📦 where this page comes from