__drm_atomic...create_state(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 __drm_atomic...create_state(9) 🌸

okay so bestie, welcome to the Kernel API Manual 💅 this one's short and sweet, like a little snack between the big scary DRM pages. let's get into it 🎀

✨ NAME ✨

__drm_atomic_helper_private_obj_create_state — literally just initializes private object state. that's the whole vibe. 🦋

✨ SYNOPSIS ✨

void __drm_atomic_helper_private_obj_create_state (struct drm_private_obj *obj , struct drm_private_state *state );

like yes, it returns void, it's not giving "i have a return value" energy, it's giving "i did the thing, move on" 💅

✨ ARGUMENTS ✨

  • obj — the private object 🫶 this is the one you're supposed to have zeroed already (see below, i'm watching you 👀)
  • state — the brand new state you want initialized ✨ freshly allocated, ready to be given a lil glow-up

✨ DESCRIPTION ✨

so what it does is initialize the newly allocated state 💖 that's it, that's the job. usually you need this when you're initializing the drivers, like it's part of the getting-ready routine, not a whole main character moment on its own.

⚠️ ngl this is important: obj is assumed to be zeroed. that's an assumption, not a suggestion. if you hand it unzeroed memory, that's on you bestie 😭 the manpage says it, i'm just the messenger 🫡

this one is useful for drivers that use private states — like if your driver is the private-state type, this is your little helper. iykyk 🌈

✨ SEE ALSO ✨

okay this list is LONG and honestly iconic, so buckle up 🎀 here's the whole friend group:

like, crtcs, planes, connectors, bridges, private objects… the whole squad showed up 💀💖

and that's the page!! short king energy, but every word of it mattered 🫶 this one lives in ./drivers/gpu/drm, dated October 2026, and it's filed under the Kernel API Manual — go read the rest of the family, they're all in SEE ALSO ✨ bye bestie, go zero your obj 💅

📦 where this page comes from