drm_atomic_...odeset_state(9)

📦 version 7.3.1, in nixpkgs unstable

✨ hey bestie, welcome to the glow-up of drm_atomic_...odeset_state(9) ✨ — yes that's the actual title, from the Kernel API Manual, and no, the ... isn't me being lazy, that's literally how it's printed 🫶

🎀 NAME 🎀

drm_atomic_helper_update_legacy_modeset_state — the little helper that goes and updates the legacy modeset state for you 💅

🦋 SYNOPSIS 🦋

void drm_atomic_helper_update_legacy_modeset_state (struct drm_device
*dev , struct drm_atomic_commit *state );

🌸 ARGUMENTS 🌸

  • dev — the DRM device, aka the thing you're doing the modeset on 💻
  • state — the atomic state object that's being committed, the whole vibe of the transaction fr fr ✨

💖 DESCRIPTION 💖

okay so here's the tea bestie 🍓 — this function goes through and updates all the various legacy modeset state pointers living in your connectors, encoders and CRTCs. Like, all of them. Every single pointer, updated, no crumbs left behind 🧚

Drivers can use this when they're building their own atomic commit — specifically if they don't have a pure helper-based modeset implementation. iykyk 😌

⚠️ now the important bit, and I need you to actually read this one: since these updates are not synchronized with lockings, only code paths called from drm_mode_config_helper_funcs.atomic_commit_tail can look at the legacy state that this helper fills out. That's the rule, no cap.

Defacto (their word, not mine, slay) this means the helper and the legacy state pointers are only really useful for transitioning an existing driver to the atomic world — it's giving "bridge era", not "forever era" 💀

🌈 SEE ALSO 🌈

okay this list is long long, but every single one of these is iconic in its own right, so here we go 👑

mwah 💋 that's the whole page. huge thanks to the fine folks in ./drivers/gpu/drm — this beauty landed in October 2026, so go read it, hydrate, and remember: lock your legacy state or it's giving chaos 🦋💅✨

📦 where this page comes from