drm_dp_mst_t...y_mgr_resume(9)

🌸 drm_dp_mst_topology_mgr_resume(9) — the Kernel API Manual glow-up ✨

okay so bestie, you found the page for drm_dp_mst_topology_mgr_resume, and it lives in the Kernel API Manual, section 9, no cap 💅. It's literally the "wake the MST manager back up" function and it's giving main character energy for your resume path. Let's get into it 🫶

---

✨ NAME ✨

drm_dp_mst_topology_mgr_resume — resume the MST manager 💖

---

✨ SYNOPSIS ✨

int drm_dp_mst_topology_mgr_resume (struct drm_dp_mst_topology_mgr *mgr
, bool sync );

---

🎀 ARGUMENTS 🎀

• mgr — the manager you're resuming, bestie. that's the whole vibe 🌈
• sync — whether or not to do the topology reprobing synchronously. yes/no, now/later, iconic either way ⭐

---

🦋 DESCRIPTION 🦋

so what this does is it fetches DPCD and checks if the device is still there 👀. if it is — slay — it rewrites the MSTM control bits and returns. done. periodt ✨

if the device fails this, it returns -1, and the driver should do a full MST reprobe, just in case we were undocked 😭 (imagine getting unplugged mid-nap, couldn't be me).

during system resume — where it's assumed that the driver will be calling drm_atomic_helper_resume — this function should be called beforehand with sync set to true 🔥

in contexts like runtime resume, where the driver is not expected to be calling drm_atomic_helper_resume, call this function with sync set to false so you don't deadlock 💀. lowkey important. highkey important actually.

---

👑 RETURN 👑

• -1 if the MST topology was removed while we were suspended 😴💔
• 0 otherwise 🎉

---

🌈 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_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_atomic_get_new_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)

---

and that's the whole page, bestie 🧚💜 this one comes straight out of ./drivers/gpu/drm/display, dated October 2026, and yes the header up top and that footer are both literally just drm_dp_mst_t...y_mgr_resume(9) — the truncation is canon, iykyk 😭🫶 go forth and resume responsibly 💅✨