drm_atomic_c..._plane_state(9)

🦋 NAME 🦋

okay so this is the manual page for drm_atomic_crtc_state_for_each_plane_state (it's a kernel API thing, from the drm_atomic_c..._plane_state(9) manual, iykyk) — and what it does is literally iterate over the attached planes in the new state ✨

💅 SYNOPSIS 💅

drm_atomic_crtc_state_for_each_plane_state (plane , plane_state ,
       crtc_state );

🌸 ARGUMENTS 🌸

• plane — bestie this is just the loop cursor, it's the thing you're looping over 🌀
• plane_state — also a loop cursor, but for the plane's state. and listen. it must be const. no cap, the const is not optional 🙈
• crtc_state — the incoming CRTC state, aka the vibe you're checking against 👑

✨ DESCRIPTION ✨

So it's giving very similar to drm_crtc_for_each_plane, except instead of just any planes, it iterates the planes that will be attached if the specified state is applied. Lowkey obsessed with the future tense of it all 🔮

It's useful during, for example, code called from drm_mode_config_funcs.atomic_check operations — that's your moment to validate the incoming state, like a little vibe check before anything actually happens 🫶

And compared to just drm_atomic_crtc_state_for_each_plane, this one also fills in a const plane_state. Which is iconic when a driver just wants to peek at other active planes on this CRTC but does not need to change it. Peek, don't touch, periodt 💅

👀 SEE ALSO 👀

• Kernel file ./include/drm/drm_atomic_helper.h — the source of truth, go read it 📖
• drm_atomic_crtc_for_each_plane(9)
• drm_atomic_crtc_state_for_each_plane(9)
• drm_atomic_plane_enabling(9)
• drm_atomic_plane_disabling(9)

okay that's the whole page, mwah 💖 comes to you from ./include/drm in the October 2026 edition of the drm_atomic_c..._plane_state(9) manual — go forth and iterate, bestie 🧚✨