tb_cfg_request_sync(9)

💖 tb_cfg_request_sync(9) 💖

okay bestie, welcome to the Kernel API Manual entry for tb_cfg_request_sync — control-request girlie is here to start a request and wait for it to finish, and honestly? iconic behavior. 🎀✨

---

🌸 NAME 🌸

tb_cfg_request_sync — Start control request and wait until it completes. periodt. 💅

---

🦋 SYNOPSIS 🦋

struct tb_cfg_result tb_cfg_request_sync (struct tb_ctl *ctl , struct
       tb_cfg_request *req , int timeout_msec );

---

🎀 ARGUMENTS 🎀

• ctl — the control channel to use, bestie. that’s the one. 🫶
• req — the request to start. go off, little request. ✨
• timeout_msec — the timeout for how long to wait for req to complete. yes, the _msec is literally right there. ⏳

---

💜 DESCRIPTION 💜

So this function starts a control request and then waits until it completes. very “I’ll wait” main character energy. 💅

If the timeout triggers, the request is canceled before the function returns. no lingering, no ghosting, it gets canceled. 😭🔥

⚠️ Important caveat: the caller needs to make sure only one message for the given switch is active at a time. not two, not a little group chat — just one. 👑

---

🌈 RETURN 🌈

It returns a struct tb_cfg_result, and if an error has occurred, the err field is non-zero. that’s your little error flag, bestie — check it. 🚩✨

---

🧚 SEE ALSO 🧚

Kernel file ./drivers/thunderbolt/ctl.c, plus these absolute icons: struct tb_ctl(9), tb_cfg_request_alloc(9), tb_cfg_request_get(9), tb_cfg_request_put(9), tb_cfg_request(9), tb_cfg_request_cancel(9), tb_ctl_alloc(9), tb_ctl_free(9), tb_ctl_start(9), tb_ctl_stop(9), tb_cfg_ack_notification(9), tb_cfg_ack_plug(9), tb_cfg_reset(9), tb_cfg_read_raw(9), tb_cfg_write_raw(9), and tb_cfg_get_upstream_port(9). iykyk. 🦋💖

---

signing off from ./drivers/thunderbolt, dated October 2026, with full tb_cfg_request_sync(9) energy — slay, and read your manpages. 💅🎀✨