drm_dp_remove_payload_part2(9)
π drm_dp_remove_payload_part2(9) β the Kernel API Manual, bestie edition π
okay so you're in the kernel API manual, section 9, and today's main character is drm_dp_remove_payload_part2 β yes the part2, don't @ me, part1 exists and she's in SEE ALSO π
β¨ NAME β¨
drm_dp_remove_payload_part2 β Remove an MST payload locally π«Ά
πΈ SYNOPSIS πΈ
void drm_dp_remove_payload_part2 (struct drm_dp_mst_topology_mgr *mgr ,
struct drm_dp_mst_topology_state *mst_state , const struct
drm_dp_mst_atomic_payload *old_payload , struct
drm_dp_mst_atomic_payload *new_payload );
like, it returns void, she gives nothing back and honestly? iconic π
π¦ ARGUMENTS π¦
mgrβ the Manager to use. the boss of the whole operation πmst_stateβ The MST atomic state β¨old_payloadβ The payload with its old state πnew_payloadβ The payload with its latest state π
π DESCRIPTION π
so here's the vibe: this function updates the starting time slots of all the other payloads β the ones that would've been shifted towards the start of the payload ID table literally just because a payload got removed. no cap, that shuffle is real π
Driver tea β: your driver should call this function whenever it removes a payload in its HW. that's the assignment, bestie, don't skip it.
and the important bit β this is independent to the result of payload allocation/deallocation at branch devices along the virtual channel. like, separate concerns, separate vibes π§ periodt.
π₯ SEE ALSO π₯
Kernel file ./drivers/gpu/drm/display/drm_dp_mst_topology.c β go read her, she ate π
then the whole friend group, fr fr:
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_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_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)
like, that's the whole group chat and every single one of them showed up ππ
okay that's the page!! she lives in ./drivers/gpu/drm/display, she's dated October 2026, and she answers to drm_dp_remove_payload_part2(9) β mwah, slay, go remove some payloads responsibly π«Άβ¨π
π¦ 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