__drm_atomi...licate_state(9)

📦 version 7.3.1, in nixpkgs unstable

💅 __drm_atomic_helper_private_obj_duplicate_state — from the Kernel API Manual, bestie

okay so picture this: it's a kernel API manual page, the vibe is immaculate, and the function name is so long it literally got truncated in the header. we love that for us. anyway. sit down, grab a strawberry 🍓, and let's talk about copying atomic private state.

✨ NAME ✨

__drm_atomic_helper_private_obj_duplicate_state — bestie, it copies atomic private state. that's the whole thing. that's the job. 💅

🦋 SYNOPSIS 🦋

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

it returns void, meaning it gives you nothing back, and honestly? iconic. it just does the thing and leaves. no notes. 👑

🌸 ARGUMENTS 🌸

  • obj — a CRTC object. that's your source material, the one holding the state we're about to steal from (lovingly). 🎀
  • state — the new private object state. this is the fresh little container the copied stuff lands in. 🫶

💖 DESCRIPTION 💖

so what it actually does: it copies atomic state from a private object's current state and then resets the inferred values. like, you take the whole vibe, but you wipe the stuff that was only ever guessed at. 🧚

and why do we care? because this is useful for drivers that subclass the private state. so if your driver is out here doing inheritance cosplay with private state, this helper has your back. periodt. 🔥

🌈 SEE ALSO 🌈

the extended universe, fr fr — everything below is 9-section kernel API realness, and yes i'm listing all of them because we don't do "etc." in this house:

ok real talk: none of this page tells you what happens if you pass something cursed. no warnings, no error codes, no exit statuses — it's void, it's chill, it just copies. don't be weird about it. 🙈

that's the whole page, bestie. sourced from ./drivers/gpu/drm and dated October 2026 — so like, future girl summer. mwah 💜✨

📦 where this page comes from