DRM_CLIENT_CAP_ATOMIC(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

DRM_CLIENT_CAP_ATOMIC(9) πŸ’…

Okay so this little icon is straight out of the Kernel API Manual, and she's here to explain atomic client caps to you, bestie. Buckle up, it's giving educational but make it cute. πŸŽ€


✨ NAME ✨

DRM_CLIENT_CAP_ATOMIC β€” (yeah, that's literally it, no description, she's mysterious πŸ’€)


✨ SYNOPSIS ✨

DRM_CLIENT_CAP_ATOMIC

That's the whole synopsis, minimal queen behavior. πŸ‘‘


✨ DESCRIPTION ✨

Okay so here's the tea, no cap. If you set this bad boy to 1, the DRM core will expose atomic properties to userspace. Periodt. And the way that it implicitly enables DRM_CLIENT_CAP_UNIVERSAL_PLANES and DRM_CLIENT_CAP_ASPECT_RATIO? It's giving package deal, iykyk. 🎁✨

But listen, if the driver doesn't support atomic mode-setting, enabling this capability will fail with -EOPNOTSUPP. So if you get that error, it's not you, it's the driver 😭. Don't take it personally, bestie.

This capability has been introduced in kernel version 4.0. Starting from kernel version 4.2, this capability is always supported for atomic-capable drivers. So if you're on 4.2+ and your driver is atomic-capable, you're absolutely slaying. πŸ”₯πŸ‘‘


✨ SEE ALSO ✨

Bestie, here's the whole friend group β€” every single one of these is part of the lore, no skips, fr fr:

Kernel file ./tools/perf/trace/beauty/include/uapi/drm/drm.h β€” here's every reference, periodt:


Big shoutout to ./tools/perf/trace/beauty/incl... for the source and October 2026 for the date β€” this page is officially signed off, periodt. πŸ’–πŸ«Ά

πŸ“¦ where this page comes from