tb_acpi_may_tunnel_pcie(9)

💅 tb_acpi_may_tunnel_pcie(9) — like, the Kernel API Manual page, bestie 💅

okay so real talk, this whole page lives in the Kernel API Manual, and the function itself is tb_acpi_may_tunnel_pcie. Say that five times fast, I dare you. 🫶

---

✨ NAME ✨

tb_acpi_may_tunnel_pcie — literally just asking the question: is PCIe tunneling allowed by the platform? That's it. That's the whole vibe check. 🦋

---

🌸 SYNOPSIS 🌸

bool tb_acpi_may_tunnel_pcie (void );

no cap, that's the entire shape of it — returns a bool, takes nothing. clean. iconic. 💅

---

🎀 ARGUMENTS 🎀

• void — no arguments. zero. nada. she takes nothing and she gives you a boolean, main character energy fr fr ✨

---

🔥 RETURN 🔥

• true — returned when a software based connection manager is used and the platform allows native PCIe tunneling 🥳
• false — otherwise, bestie. anything else, and it's a no. 😭

that's the whole deal — both conditions gotta be a yes for the true to hit. highkey simple.

---

⭐ SEE ALSO ⭐

the kernel file we're living in: ./drivers/thunderbolt/acpi.c

and the whole friend group of related functions, all of them, every single one, no skipping:

• tb_acpi_add_links(9)
• tb_acpi_is_native(9)
• tb_acpi_may_tunnel_usb3(9)
• tb_acpi_may_tunnel_dp(9)
• tb_acpi_is_xdomain_allowed(9)
• tb_acpi_power_on_retimers(9)
• tb_acpi_power_off_retimers(9)

go read those next, iykyk 🧚

---

lowkey important: this page is from ./drivers/thunderbolt, and the version stamp on it says October 2026 — so yeah, she's dated, she's sourced, she's official. periodt. 👑

💖 okay bye, go tunnel some PCIe (but only if the platform says it's allowed, obviously) 💖