drm_for_each_crtc_reverse(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

drm_for_each_crtc_reverse(9) β€” from the Kernel API Manual, bestie β€” is literally the reverse-order CRTC loop. The NAME line says it all: iterate over all CRTCs in reverse order. Periodt. πŸ’…βœ¨


✨ SYNOPSIS ✨

Ok so the synopsis is giving exactly this, no cap:

drm_for_each_crtc_reverse (crtc , dev );

πŸ’… ARGUMENTS πŸ’…

  • crtc β€” a struct drm_crtc as the loop cursor. She’s your main-character cursor for this whole loop, okay? πŸŽ€
  • dev β€” the struct drm_device. This is the device vibe we’re working with, fr fr. πŸ¦‹

πŸ¦‹ DESCRIPTION πŸ¦‹

Iterate over all CRTCs of dev.

That’s the whole description, bestie β€” no hidden lore, no extra side quests. The reverse-order part is already iconic in the NAME, so we’re just looping over every CRTC of dev and letting the reverse energy do its thing. πŸŒˆπŸ’–


πŸ”₯ SEE ALSO πŸ”₯


Cute sign-off time, bestie: source/version is ./include/drm, date is October 2026, and this iconic page is drm_for_each_crtc_reverse(9). Byeee πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from