drm_dp_remove_payload_part2(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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:

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