drm_atomic_...pology_state(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

okay so this is the page for drm_atomic_...pology_state(9) β€” yes the header truncates it, iconic of man to do that β€” and the actual star of the show is drm_atomic_get_new_mst_topology_state, which gets you the new MST topology state inside an atomic state, if there even is one ✨


🌸 SYNOPSIS 🌸

struct drm_dp_mst_topology_state * drm_atomic_get_new_mst_topology_state
(struct drm_atomic_commit *state , struct drm_dp_mst_topology_mgr *mgr
);

πŸŽ€ ARGUMENTS πŸŽ€

  • state β€” the global atomic state, bestie. the big one. the main character 🌈
  • mgr β€” the MST topology manager, which is also the private object in this case, iykyk πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

So the way this works πŸ‘‘ β€” this function is literally just wrapping drm_atomic_get_new_private_obj_state, and it passes in the MST atomic state vtable so that the private object state you get back is the state of an MST topology object. that's it. that's the whole vibe. no cap 🫢


⭐ RETURN ⭐

You get the new MST topology state πŸŽ‰ β€” or NULL if there's no topology state for this MST mgr in the global atomic state 😭 (yes, NULL is a possible answer, don't come for me).

fr fr check for that NULL before you go dereferencing, bestie πŸ’€

πŸ’œ SEE ALSO πŸ’œ

like. that's a lot of friends. go read them, they're all slaying in their own way πŸ§šβ€β™€οΈ


and that's the page!! πŸ’– this gem lives in ./drivers/gpu/drm/display, dated October 2026, and it's the drm_atomic_...pology_state(9) page β€” mwah, go get that topology state bestie πŸ“βœ¨

πŸ“¦ where this page comes from