drm_atomic_...crtc_disable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_atomic_...crtc_disable(9) πŸ’…

okay bestie, quick vibe check first β€” this page lives in the Kernel API Manual, and the function it's hyping up is drm_atomic_helper_commit_crtc_disable. yes, the page title is the dramatic abbreviated version, we don't make the rules ✨


✨ NAME ✨

drm_atomic_helper_commit_crtc_disable β€” disable CRTSs 🫢


🌸 SYNOPSIS 🌸

void drm_atomic_helper_commit_crtc_disable (struct drm_device *dev ,
       struct drm_atomic_commit *state );

like… that's the whole signature, no cap πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the DRM device, your main character πŸ–₯️
  • state β€” the driver state object, aka the whole situation we're working with πŸ¦‹

⭐ DESCRIPTION ⭐

okay so here's the tea πŸ“ β€” this function loops over all the CRTCs in the current state, and if a CRTC needs it, it disables it. that's it, that's the whole personality. lowkey iconic in how straightforward it is πŸ‘‘

to say it again in my own words but with all the same facts: it loops over all CRTCs in the current state, and if the CRTC needs it, it disables it. periodt πŸ’œ


πŸ”₯ SEE ALSO πŸ”₯

ngl the see-also section here is giving whole extended friend group β€” every single one of these is invited to the party πŸŽ‰:


that's the whole page bestie, go disable some CRTSs responsibly πŸ’–βœ¨

oh and before i forget β€” this whole thing is filed under ./drivers/gpu/drm and it's dated October 2026, so like… future energy πŸŒˆπŸ¦‹ mwah, bye πŸŽ€

πŸ“¦ where this page comes from