drm_atomic_g...olorop_state(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_atomic_g...olorop_state — a Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual page for drm_atomic_g...olorop_state(9) — yes the name is doing a little ellipsis thing, we love an abbreviated icon ✨

🌸 NAME 🌸

drm_atomic_get_colorop_state — literally just get the colorop state, that's the whole job, no cap 💖

🦋 SYNOPSIS 🦋

struct drm_colorop_state * drm_atomic_get_colorop_state (struct
drm_atomic_commit *state , struct drm_colorop *colorop );

like, that's the whole signature, copy it exactly bestie 🫶

🎀 ARGUMENTS 🎀

  • state — the global atomic state object. yes global, she's the main character of this whole operation 👑
  • colorop — the colorop you want the state object for. that's the one. that's your girl 💜

🔥 DESCRIPTION 🔥

So what does this function do?? It returns the colorop state for the given colorop — and if that state doesn't exist yet? it allocates it, because it's an icon and it handles things 💅✨

It also grabs the relevant plane lock to make sure that the state is consistent. gotta protect the vibe check, y'know? 🔒

What you get back is either:

  • the allocated state, or
  • the error code encoded into the pointer
⚠️ okay this part matters bestie: when the error is EDEADLK, the w/w mutex code has detected a deadlock and the entire atomic sequence must be restarted. like, the whole thing. start over. no shortcuts 😭

All other errors are fatal. not cute. not recoverable. fatal fr fr 💀

🌈 SEE ALSO 🌈

OK this list is LONG and every single one of these is staying, because I would never do my besties dirty by skipping entries 🍓

Kernel file ./drivers/gpu/drm/drm_atomic.c, plus:

like, the whole friend group showed up 😭💖

🧚 sign-off 🧚

this lil masterpiece lives in ./drivers/gpu/drm, dated October 2026 — go read it, it's giving kernel dev excellence, iykyk 🌸✨🫶

📦 where this page comes from