drm_atomic_...rop_for_crtc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_atomic_set_mode_prop_for_crtc β€” Kernel API Manual ✨

okay so real talk, bestie, this is a page straight out of the Linux kernel API manual β€” like, the actual Kernel API Manual, no cap 🫢. The full name of the function is drm_atomic_set_mode_prop_for_crtc, and yeah the page header gets truncated to drm_atomic_...rop_for_crtc(9) because terminals are dramatic and love a cliffhanger 😭. Anyway. Sit down, grab a strawberry drink πŸ“, and let's get into it.


🌸 NAME 🌸

drm_atomic_set_mode_prop_for_crtc β€” set the mode for a CRTC, but make it blob πŸ’…


✨ SYNOPSIS ✨

int drm_atomic_set_mode_prop_for_crtc(struct drm_crtc_state *state,
                                      struct drm_property_blob *blob);

πŸŽ€ ARGUMENTS πŸŽ€

  • state β€” the CRTC whose incoming state we're updating. she's the main character here πŸ‘‘
  • blob β€” a pointer to the blob property to use for the mode. like, the vibe source 🌈

πŸ¦‹ DESCRIPTION πŸ¦‹

So what she does is: she sets a mode on the CRTC state you want, and that mode originates from a blob property. iconic behavior, honestly.

The way this works is she takes a reference on the blob property for the CRTC state πŸ’– β€” and at the same time she releases the reference held on the state's existing mode property, if any was set. so it's giving responsible refcounting queen, no leaks, we stan 🧚✨


πŸ”₯ RETURN πŸ”₯

  • Zero on success πŸ’š (slay)
  • An error code on failure πŸ’€
  • She cannot return -EDEADLK β€” literally not possible, don't even worry about it πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘


bestie this whole page lives in ./drivers/gpu/drm β€” that's the directory, she's at home there 🏑

and that's the whole thing!! from your girl, dated October 2026, filed under the drm_atomic_...rop_for_crtc(9) header because some things in life are just truncated πŸ’œ mwah, go set some modes πŸŽ€βœ¨

πŸ“¦ where this page comes from