drm_atomic_c...r_each_plane(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

drm_atomic_crtc_for_each_plane β€” okay so this one iterates over the planes that are currently attached to a CRTC πŸ¦‹


✨ SYNOPSIS ✨

drm_atomic_crtc_for_each_plane (plane , crtc );

(it's a macro, bestie, so yes the spacing is a whole vibe 😭 keep it exactly like that)


πŸŽ€ ARGUMENTS πŸŽ€

  • plane β€” this is your loop cursor πŸ‘‘ like, the variable that hops from plane to plane while you're looping.
  • crtc β€” the CRTC whose planes are getting iterated πŸ’… that's the one you're looking at.

🌸 DESCRIPTION 🌸

So here's the tea: this iterates over the current state ⭐ useful, for example, when you're applying atomic state after it's already been checked and swapped. Lowkey the "we're done deciding, now commit" moment 🫢

But if you want to iterate over the planes that will be attached β€” which is, ngl, more useful in code called from drm_mode_config_funcs.atomic_check β€” then you want drm_atomic_crtc_state_for_each_plane instead πŸ‘€βœ¨ iykyk.

fr fr though, don't mix these two up β€” one is "what's attached rn", the other is "what's about to be attached". Different vibes, different macros, no cap πŸ’€

πŸ”₯ SEE ALSO πŸ”₯


and that's the whole page, periodt πŸ’… This little icon lives over in ./include/drm, dated October 2026, and the header on it is drm_atomic_c...r_each_plane(9) β€” mwah, go slay some atomic state πŸ§šπŸ’œ

πŸ“¦ where this page comes from