__drm_atomic...r_crtc_reset(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __drm_atomic_helper_crtc_reset β€” the unofficial group chat edition

okay so real talk, this is a page from the Kernel API Manual (yes, the Kernel API Manual, we're fancy now ✨) and it's about resetting state on a CRTC. buckle up bestie, it's shorter than you'd think but every word matters πŸŽ€


✨ NAME ✨

__drm_atomic_helper_crtc_reset β€” reset state on CRTC πŸ¦‹

🌸 SYNOPSIS 🌸

void __drm_atomic_helper_crtc_reset (struct drm_crtc *crtc , struct
drm_crtc_state *crtc_state );

πŸ’– ARGUMENTS πŸ’–

  • crtc β€” the drm CRTC. that's the thing you're resetting, the main character of this whole operation πŸ‘‘
  • crtc_state β€” the CRTC state to assign. this is the fresh little state you're handing over 🫢

πŸ”₯ DESCRIPTION πŸ”₯

So what does it do? It initializes the newly allocated crtc_state and assigns it to the drm_crtc->state pointer of crtc. literally that's the whole vibe ✨

When do you need it? usually when initializing the drivers, or when it gets called from the drm_crtc_funcs.reset hook. so like, two very real situations ngl.

And why does this exist? it's useful for drivers that subclass the CRTC state πŸ’… β€” if your driver is doing the subclass thing, this helper is your bestie fr fr.

lowkey important: this is the double-underscore version, the internal-ish one. it's not doing the full song and dance, it's just doing the init-and-assign part πŸŽ€

🌈 SEE ALSO 🌈

okay this list is long long, but we're not skipping it, we don't do that here 😭 everything gets its moment:

like… crtc, plane, connector, private_obj, bridge β€” the whole atomic helper family reunion 🧚


anyway that's the page!! go reset some CRTC state, you got this πŸ’œ

this little broadcast came from ./drivers/gpu/drm, dated October 2026, and it's filed under __drm_atomic...r_crtc_reset(9) in the Kernel API Manual β€” bye bestie, drink water πŸ“βœ¨

πŸ“¦ where this page comes from