drm_dp_add_payload_part2(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_dp_add_payload_part2(9) — from the Kernel API Manual ✨

okay so bestie, this is a page from the Kernel API Manual, and it's about drm_dp_add_payload_part2 — the second half of the whole "give this payload a time slot" saga. she's the finisher, the closer, the one who actually sends the messages. let's get into it 🎀

✨ NAME ✨

drm_dp_add_payload_part2 — Execute payload update part 2. literally the part 2. the sequel that slays 💅

🌸 SYNOPSIS 🌸

int drm_dp_add_payload_part2 (struct drm_dp_mst_topology_mgr *mgr ,
struct drm_dp_mst_atomic_payload *payload );

🦋 ARGUMENTS 🦋

  • mgr — Manager to use. the main character here, the one running the whole topology show 👑
  • payload — The payload to update. yes queen, this is the one getting her glow-up ✨

💖 DESCRIPTION 💖

okay so here's the lore 🫶 if payload was successfully assigned a starting time slot by drm_dp_add_payload_part1, then this function will send the sideband messages to finish allocating this payload. that's it, that's the whole vibe — part 1 sets her up, part 2 sends the messages and actually seals the deal. teamwork, no cap 🤝

heads up bestie: if part 1 didn't successfully give her a starting time slot, then this part-2 moment doesn't happen. the condition is literally in the sentence 💀

⭐ RETURN ⭐

0 on success, negative error code on failure. so like, zero = slay, negative = we're sobbing 😭

🌈 SEE ALSO 🌈

the whole friend group, fr fr — every single one of them:

and that's the whole page, bestie — go forth and allocate those payloads 💜

mwah 💋 this drop came from ./drivers/gpu/drm/display, dated October 2026, and it's the drm_dp_add_payload_part2(9) page — catch you in part 1 🎀

📦 where this page comes from