drm_atomic_check_only(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_atomic_check_only β€” a vibe check for your atomic config

okay so bestie, this one's from the Kernel API Manual, and it's genuinely iconic: it's the "will this even work tho" function. No cap. πŸ‘‘


✨ NAME ✨

drm_atomic_check_only β€” check whether a given config would work 🫢


🌸 SYNOPSIS 🌸

int drm_atomic_check_only (struct drm_atomic_commit *state );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • state β€” the atomic configuration you want to check. that's it, that's the whole argument, she's lowkey simple πŸ’…

πŸŽ€ DESCRIPTION πŸŽ€

So like, real talk: this function can return -EDEADLK 😭 and that happens when the driver needed to grab more locks but hit a deadlock. Not the fun kind of deadlock, the kernel kind.

When that happens, the caller must then do the usual w/w backoff dance and restart. the w/w backoff dance is a whole thing, but it's the standard move β€” you back off, you retry, you slay πŸ’ƒ

⚠️ Every other error is fatal. not "oops retry" fatal β€” actually fatal. so if you get anything that isn't -EDEADLK, do not come for the retry, because it's not giving second chances πŸ’€

🌈 RETURN 🌈

  • 0 on success β€” we ate, no notes ✨
  • a negative error code on failure β€” she's not okay, bestie πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/gpu/drm/drm_atomic.c, plus the whole friend group:


and that's the whole page, bestie πŸ’– this one lives in the kernel docs under ./drivers/gpu/drm, it's tagged October 2026, and it's part of the Kernel API Manual. periodt. πŸŽ€βœ¨

πŸ“¦ where this page comes from