drm_dp_mst_..._new_request(9)

💅 drm_dp_mst_hpd_irq_send_new_request 💅

okay so first things first, bestie: this page lives in the Kernel API Manual, and the full name is lowkey a keyboard smash — drm_dp_mst_hpd_irq_send_new_request. the header up top abbreviates it to drm_dp_mst_..._new_request(9) because nobody has time to type all that. anyway. let's get into it 💖

---

✨ NAME ✨

drm_dp_mst_hpd_irq_send_new_request — MST hotplug IRQ kick off new request. that's the whole vibe. it kicks off a new request. slay 🔥

---

✨ SYNOPSIS ✨

void drm_dp_mst_hpd_irq_send_new_request (struct drm_dp_mst_topology_mgr
*mgr );

---

✨ ARGUMENTS ✨

• mgr — the manager to notify irq for. that's it, that's the whole argument, she's a one-argument icon 👑

---

✨ DESCRIPTION ✨

okay so here's the tea 🍵 — you call this from the driver when an MST irq event is handled and acked. both. the handling and the acking. don't skip a step, bestie.

⚠️ and this is the part where you really need to pay attention: a new down request should only be sent when the previous message transaction is completed. the source is not supposed to generate interleaved message transactions. like, literally not. no overlapping, no interleaving, no "oops I sent two at once" energy. finish your message transaction before you start the next one, periodt 💅

it's giving "one thing at a time" and honestly? iconic behavior. main character energy fr fr 💀

---

🌈 SEE ALSO 🌈

grab a snack and sit down because this list is long, I'm not even kidding 😭 the kernel file lives at ./drivers/gpu/drm/display/drm_dp_mst_topology.c, and then we have:

• 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_topology_mgr_resume(9)
• drm_dp_mst_hpd_irq_handle_event(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)

see? told you it was a lot. every single one of them, bestie, we don't gatekeep 🫶

---

that's the page!! mwah 💋 ok bye, this came from ./drivers/gpu/drm/display, dated October 2026, and the page itself is drm_dp_mst_..._new_request(9) — go read the other fifty-seven(9) pages, ily, drink some water 🌸🧚💜