drm_atomic_c...r_each_plane(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ drm_atomic_c...r_each_plane(9) ✨

okay bestie so this is a page straight out of the Kernel API Manual and honestly it's giving "niche but iconic" πŸ’… like nobody at brunch is gonna bring this up but the people who need it need it, iykyk 🫢


🌸 NAME 🌸

drm_atomic_crtc_state_for_each_plane β€” bestie, this one literally iterates over the planes that are attached in the new state πŸ¦‹


⭐ SYNOPSIS ⭐

drm_atomic_crtc_state_for_each_plane (plane , crtc_state );

like yes, that's the whole thing. she's a macro, she's a loop, she's a main character πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • plane β€” the loop cursor πŸ’« this is the little variable that like, walks through every plane one at a time. she's doing the rounds, she's the one moving.
  • crtc_state β€” the incoming CRTC state 🌈 the state you're passing in, bestie, the one you're checking out.

πŸ’– DESCRIPTION πŸ’–

so this is lowkey a sibling of drm_crtc_for_each_plane, right? same energy, but with a plot twist ✨ instead of iterating whatever planes are around right now, this one iterates the planes that will be attached if the specified state is applied πŸ”₯ which is a whole different vibe, ngl.

and that is literally so useful β€” for example, in code called from drm_mode_config_funcs.atomic_check operations, where the whole entire point is to validate the incoming state πŸ’… like, vibe check the state before it becomes real. periodt.


πŸ¦‹ SEE ALSO πŸ¦‹


okay that's the page!! πŸŽ€ and for the cute little sign-off β€” this one lives under ./include/drm, and the manual's dated October 2026 πŸ’œ so like, mark your calendars bestie, the planes are planning ahead 😭🌸

πŸ“¦ where this page comes from