drm_atomic_g...te_obj_state(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_atomic_get_private_obj_state(9)

okay so bestie, welcome to the Kernel API Manual ✨ this one's short and sweet, and it's literally about grabbing private object state. let's get into it 🫢


🌸 NAME 🌸

drm_atomic_get_private_obj_state β€” get private object state

✨ SYNOPSIS ✨

struct drm_private_state * drm_atomic_get_private_obj_state (struct drm_atomic_commit *state , struct drm_private_obj *obj );

πŸŽ€ ARGUMENTS πŸŽ€

  • state β€” the global atomic state, periodt
  • obj β€” the private object you're getting the state for, iykyk

πŸ’– DESCRIPTION πŸ’–

so this function returns the private object state for the given private object β€” and the way it does that is it allocates the state if it's needed. not optional, just bestie things πŸ’…

it also grabs the relevant private object lock, because we need that state to be consistent. no cap, the lock matters.

πŸ”₯ RETURN πŸ”₯

either the allocated state, or the error code encoded into a pointer. that's it, that's the vibe check ⭐

πŸ¦‹ SEE ALSO πŸ¦‹


ok that's the whole page bestie, no crumbs left behind πŸ™ˆ go read the source if you wanna know more, mwah πŸ’œ

and that's a wrap on this one, brought to you by ./drivers/gpu/drm, dated October 2026, filed under drm_atomic_g...te_obj_state(9) 🌈 slay πŸŽ€

πŸ“¦ where this page comes from