drm_atomic_h...r_reset_crtc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ drm_atomic_helper_reset_crtc ✨

Okay bestie, welcome to the Kernel API Manual, section 9 β€” this one's about drm_atomic_helper_reset_crtc, the little function that hits the reset button on a CRTC's active outputs. It's giving "have you tried turning it off and on again" but for display hardware πŸ’…


🌸 NAME 🌸

drm_atomic_helper_reset_crtc β€” reset the active outputs of a CRTC


πŸŽ€ SYNOPSIS πŸŽ€

int drm_atomic_helper_reset_crtc (struct drm_crtc *crtc , struct
       drm_modeset_acquire_ctx *ctx );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • crtc β€” the DRM CRTC, i.e. the thing you're resetting. Main character energy, obviously.
  • ctx β€” the lock acquisition context. It's the vibe check for your locks, no cap.

πŸ’– DESCRIPTION πŸ’–

So what does it actually do? It resets the active outputs by indicating that connectors have changed. And because of that, it implies a reset of every active component chilling between the CRTC and the connectors β€” like, the whole little ecosystem gets refreshed together, periodt.

Also, a lil' sibling exists: drm_bridge_helper_reset_crtc, which is the same idea but dedicated to bridges. Different function, same slay 🫢


⚠️ NOTE ⚠️

This whole thing relies on resetting drm_crtc_state.connectors_changed. So for drivers that optimize out unnecessary modesets β€” yeah, this will result in a no-op commit. It achieves nothing. Literally nothing. Not a single thing. πŸ˜­πŸ’€

Not a bug, just how it is β€” so don't come for the function when your driver's optimizer eats it for breakfast.


πŸ‘‘ RETURN πŸ‘‘

0 on success, or a negative error code on failure. That's it, that's the whole vibe check 🌈


🧚 SEE ALSO 🧚

Grab a snack, bestie, because this list is long β€” but every single one of these is here for a reason, iykyk:


That's the whole page, bestie β€” you ate that πŸ“

πŸ’œ Cute lil' sign-off: this one lives in ./drivers/gpu/drm, dated October 2026, and it goes by drm_atomic_h...r_reset_crtc(9) because apparently even manpage headers gotta be mysterious. ✨

πŸ“¦ where this page comes from