drm_atomic_...pology_state(9)
π 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 π
- Kernel file
./drivers/gpu/drm/display/drm_dp_mst_topology.c dp mst helper(9)Branch device and port refcounting(9)drm_dp_mst_get_mstb_malloc(9)drm_dp_mst_put_mstb_malloc(9)drm_dp_mst_get_port_malloc(9)drm_dp_mst_put_port_malloc(9)drm_dp_mst_topology_try_get_mstb(9)drm_dp_mst_topology_get_mstb(9)drm_dp_mst_topology_put_mstb(9)drm_dp_mst_topology_try_get_port(9)drm_dp_mst_topology_get_port(9)drm_dp_mst_topology_put_port(9)drm_dp_mst_dpcd_read(9)drm_dp_mst_dpcd_write(9)drm_dp_mst_connector_late_register(9)drm_dp_mst_connector_early_unregister(9)drm_dp_add_payload_part1(9)drm_dp_remove_payload_part1(9)drm_dp_remove_payload_part2(9)drm_dp_add_payload_part2(9)drm_dp_get_vc_payload_bw(9)drm_dp_read_mst_cap(9)drm_dp_mst_topology_mgr_set_mst(9)drm_dp_mst_topology_queue_probe(9)drm_dp_mst_topology_mgr_suspend(9)drm_dp_mst_topology_mgr_resume(9)drm_dp_mst_hpd_irq_handle_event(9)drm_dp_mst_hpd_irq_send_new_request(9)drm_dp_mst_detect_port(9)drm_dp_mst_edid_read(9)drm_dp_mst_get_edid(9)drm_dp_atomic_find_time_slots(9)drm_dp_atomic_release_time_slots(9)drm_dp_mst_atomic_setup_commit(9)drm_dp_mst_atomic_wait_for_dependencies(9)drm_dp_mst_root_conn_atomic_check(9)drm_dp_mst_update_slots(9)drm_dp_check_act_status(9)drm_dp_calc_pbn_mode(9)drm_dp_mst_dump_topology(9)drm_dp_mst_port_downstream_of_parent(9)drm_dp_mst_add_affected_dsc_crtcs(9)drm_dp_mst_atomic_enable_dsc(9)drm_dp_mst_atomic_check_mgr(9)drm_dp_mst_atomic_check(9)drm_atomic_get_mst_topology_state(9)drm_atomic_get_old_mst_topology_state(9)drm_dp_mst_topology_mgr_init(9)drm_dp_mst_topology_mgr_destroy(9)drm_dp_mst_register_i2c_bus(9)drm_dp_mst_unregister_i2c_bus(9)drm_dp_mst_is_virtual_dpcd(9)drm_dp_mst_aux_for_parent(9)drm_dp_mst_dsc_aux_for_port(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms