drm_atomic_h...check_planes(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

okay so bestie, welcome to the drm_atomic_h...check_planes(9) page from the Kernel API Manual ✨ this is the function that does a vibe check on your state object specifically for plane changes β€” validate state object for planes changes, periodt.

✨ SYNOPSIS ✨

int drm_atomic_helper_check_planes (struct drm_device *dev , struct
drm_atomic_commit *state );

🫢 ARGUMENTS 🫢

  • dev β€” the DRM device. It's the main-character device context for this check πŸŽ€
  • state β€” the driver state object, aka the thing we're about to inspect and validate.

🧚 DESCRIPTION 🧚

So the whole assignment is checking the state object to see if the requested state is physically possible. Not "wouldn't it be cute if this worked" β€” physically possible, bestie. It does all the plane update related checks by calling into the drm_crtc_helper_funcs.atomic_check and drm_plane_helper_funcs.atomic_check hooks provided by the driver πŸ’…

It also sets drm_crtc_state.planes_changed to indicate that a CRTC has updated planes. Yes, that's the little flag situation β€” it literally says a CRTC has updated planes.

🌈 RETURN 🌈

Zero for success, or -errno. That's the whole return vibe check, no cap 😌

πŸ”₯ SEE ALSO πŸ”₯

these besties are also serving manpage realness ✨


byeee bestie πŸŽ€ this page is brought to you by the source/version corner: ./drivers/gpu/drm, dated October 2026, and the footer flex is literally drm_atomic_h...check_planes(9). mwah πŸ’–

πŸ“¦ where this page comes from