drm_atomic_c...ively_active(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_atomic_c...ively_active β€” a Kernel API Manual moment ✨

okay bestie, so this one lives in the Kernel API Manual and it's genuinely so useful once you get what it's doing. it's giving "don't trust active, trust the vibe check" 🫢


🌸 NAME 🌸

drm_atomic_crtc_effectively_active β€” compute whether a CRTC is actually active, for real for real


✨ SYNOPSIS ✨

bool drm_atomic_crtc_effectively_active (const struct drm_crtc_state *state );

πŸŽ€ ARGUMENTS πŸŽ€

  • state β€” the drm_crtc_state for the CRTC. that's it, that's the whole argument, she's low maintenance πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the situation, and it's kind of a plot twist 😭

when you're in self refresh mode, the crtc_state->active value is gonna be false, because the CRTC is off. like, genuinely off. no cap.

BUT β€” and this is the main character energy part β€” sometimes we're actually interested in whether the CRTC is active, or effectively active (ie: it's connected to an active display). so the thing is still doing something even though active is screaming false at you πŸ’€

in those cases? use this function instead of just checking active. that's the whole assignment, bestie. don't just peek at active and call it a day, use the icon it deserves πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

  • Kernel file ./include/drm/drm_atomic.h

and now the whole friend group, gather round 🧚:


mwah πŸ’‹ this page came from ./include/drm, dated October 2026, and honestly? iconic. go check your CRTC's vibe bestie, ily, bye πŸŽ€βœ¨

πŸ“¦ where this page comes from