tb_cfg_get_upstream_port(9)

💅 tb_cfg_get_upstream_port(9) 💅

okay so welcome to the Kernel API Manual entry for tb_cfg_get_upstream_port(9) — yes bestie, the manual name is literally Kernel API Manual, and we’re folding that in right here instead of doing the whole header-line situation 💖

---

🌸 NAME 🌸

tb_cfg_get_upstream_port — get upstream port number of switch at route

---

✨ SYNOPSIS ✨

int tb_cfg_get_upstream_port (struct tb_ctl *ctl , u64 route );

---

🫶 ARGUMENTS 🫶

• ctl — pointer to the control channel, aka the control-channel pointer bestie 🎀
• route — the route string of the router, exactly that 🌈

---

💖 DESCRIPTION 💖

So it reads the first dword from the switches TB_CFG_SWITCH config area and returns the port number from which the reply originated. That’s the whole vibe: first dword, TB_CFG_SWITCH config area, reply-origin port number. No cap, it’s giving tiny-helper energy 🧚✨

---

🔥 RETURN 🔥

Upstream port number on success, or a negative error code on failure. Periodt 💅

lowkey important: success = upstream port number, failure = negative error code. Keep that energy, bestie.

---

👀 SEE ALSO 👀

• Kernel file ./drivers/thunderbolt/ctl.c
• 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_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)

---

mwah 💋 — sent with love from ./drivers/thunderbolt, dated October 2026, on page tb_cfg_get_upstream_port(9) 🎀🦋