drm_atomic_get_crtc_state(9)

📦 version 7.3.1, in nixpkgs unstable

Okay bestie, let's talk about drm_atomic_get_crtc_state(9) from the Kernel API Manual — this one's a banger. 💅

✨ NAME ✨

drm_atomic_get_crtc_state — get CRTC state. Periodt, that's the whole name.

🦋 SYNOPSIS 🦋

struct drm_crtc_state * drm_atomic_get_crtc_state (struct drm_atomic_commit *state , struct drm_crtc *crtc );

🎀 ARGUMENTS 🎀

  • state — the global atomic state object. Think of it as the group chat where all the atomic stuff gets coordinated. 🌐
  • crtc — the CRTC you want the state object for. It's the screen controller, and it's the main character of this call. 👑

💖 DESCRIPTION 💖

So here's the tea: this function literally returns the CRTC state for the CRTC you gave it, and if that state doesn't exist yet, it allocates it on the spot — no cap. It also grabs the relevant CRTC lock to make sure the state stays consistent, because we don't do messy half-updated vibes around here. 🔒✨

⚠️ WARNING ⚠️ — Drivers can only add new CRTC states to a state if drm_atomic_commit.allow_modeset is set, OR if it's a driver-internal commit that userspace didn't create through an IOCTL call. That's the rule, bestie, and you better respect it. 💀

🔥 RETURN 🔥

You get back either the allocated state or an error code encoded into the pointer. When the error is EDEADLK, that means the w/w mutex code has detected a deadlock and the entire atomic sequence must be restarted — it's giving "try again from the top, bestie." 🔁 Every other error is fatal, and I mean fatal fatal. No survivors. 💀

🌈 SEE ALSO 🌈

This function is besties with a whole squad. Check out:

This slay page was brought to you by the kernel file ./drivers/gpu/drm, dated October 2026, for drm_atomic_get_crtc_state(9). Bye bestie! 💅✨🦋

📦 where this page comes from