tb_cfg_request(9)

💖 NAME 💖

tb_cfg_request — Start control request not waiting for it to complete.

Hi bestie! You're in the Kernel API Manual, on the tb_cfg_request(9) page. Strap in, this one's short and sweet 🎀

---

✨ SYNOPSIS ✨

The whole signature, exactly, no edits:

int tb_cfg_request (struct tb_ctl *ctl , struct tb_cfg_request *req ,
void (*callback)(void *) , void *callback_data );

---

🦋 ARGUMENTS 🦋

• ctl — the control channel to use, periodt.
• req — the request to start. Like, actually start it, bestie.
• callback — callback called when the request is completed. Main character energy.
• callback_data — data to be passed to callback.

---

🌸 DESCRIPTION 🌸

Okay so this is lowkey the async one: it queues req on the given control channel without waiting for it to complete. Then, when the request completes, callback is called. That's the whole vibe, and it's iconic ✨

---

🔥 RETURN 🔥

0 on success, negative errno otherwise. No cap, that's the return contract 💅

---

👑 SEE ALSO 👑

Go vibe with these, bestie:

• Kernel file ./drivers/thunderbolt/ctl.c + struct tb_ctl(9) — the kernel file and the struct, iykyk.
• tb_cfg_request_alloc(9)
• tb_cfg_request_get(9)
• tb_cfg_request_put(9)
• tb_cfg_request_cancel(9)
• tb_cfg_request_sync(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)
• tb_cfg_get_upstream_port(9)

---

Okay that's the whole page, bestie 💖 It's from ./drivers/thunderbolt, dated October 2026, and it's tb_cfg_request(9) from the Kernel API Manual — bye, love you, slay 🎀