drm_dp_mst_..._mgr_suspend(9)
π drm_dp_mst_topology_mgr_suspend(9) β the kernel API manual, but make it make sense
okay so bestie, you're looking at the manual page for drm_dp_mst_topology_mgr_suspend(9) β yes that's a whole mouthful, the title literally has an ellipsis in it (iconic honestly) β and it's filed under the Kernel API Manual. Welcome to the DisplayPort MST zone, it's cozy here π
β¨ NAME β¨
drm_dp_mst_topology_mgr_suspend β suspend the MST manager. that's it. that's the whole vibe. your topology manager is going night-night π΄
β¨ SYNOPSIS β¨
void drm_dp_mst_topology_mgr_suspend (struct drm_dp_mst_topology_mgr
*mgr );
no return value, it just does the thing and dips. we love a void function with no notes π
β¨ ARGUMENTS β¨
mgrβ the manager you're putting to sleep. the MST topology manager that's about to be suspended. give it a lil forehead kiss π«Ά
β¨ DESCRIPTION β¨
okay so here's what's actually happening. drm_dp_mst_topology_mgr_suspend tells the MST device that we literally cannot handle UP messages anymore β like, we're not ignoring you on purpose, we're just suspended, bestie π
and the whole point of telling it? so it stops sending them. because if we're suspended and it keeps firing UP messages at us, that's just chaos for no reason. so we announce the suspend, the device respects it, and nobody's sending messages into the void. clean. slay. periodt β¨
β¨ SEE ALSO β¨
the whole friend group, no cap π«Ά β go read ./drivers/gpu/drm/display/drm_dp_mst_topology.c first, it's giving main character energy:
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_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_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)
heads up bestie: if you suspend the manager, it literally cannot handle UP messages until you bring it back. don't be out here expecting messages mid-nap π
π and that's the page!! sign-off time: this one lives under ./drivers/gpu/drm/display, it's dated October 2026, and the whole thing is filed as drm_dp_mst_..._mgr_suspend(9) β go put your manager to sleep, queen πβ¨
π¦ 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