tb_acpi_is_native(9)

🌸 tb_acpi_is_native(9) 🌸

okay bestie, welcome to the Kernel API Manual — this one is short and iconic. It’s the entry for tb_acpi_is_native(9), and it’s basically asking: did the platform grant native TBT/USB4 control? 💅

---

✨ NAME ✨

tb_acpi_is_native — did the platform grant native TBT/USB4 control?

🎀 SYNOPSIS 🎀

bool tb_acpi_is_native (void );

🫶 ARGUMENTS 🫶

• void — no arguments. literally none. zero. the void is voiding. 😭

🦋 RETURN 🦋

• true — if the platform granted OS native control over TBT/USB4. slay.
• false — otherwise. no native control, no cap.

So yeah: it returns true if the platform granted OS native control over TBT/USB4, and false otherwise. ✨

💖 DESCRIPTION 💖

When returned true, software based connection manager can be used, otherwise there is firmware based connection manager running.

That’s the whole tea. When it comes back true, the software based connection manager can be used. When it doesn’t? There’s a firmware based connection manager running. main character energy either way 👑

🌈 SEE ALSO 🌈

• Kernel file ./drivers/thunderbolt/acpi.c — the source bestie.
• tb_acpi_add_links(9)
• tb_acpi_may_tunnel_usb3(9)
• tb_acpi_may_tunnel_dp(9)
• tb_acpi_may_tunnel_pcie(9)
• tb_acpi_is_xdomain_allowed(9)
• tb_acpi_power_on_retimers(9)
• tb_acpi_power_off_retimers(9)

go read those too, iykyk 🧚

---

catch you in the next manpage, bestie 💅 — source/version: ./drivers/thunderbolt, dated October 2026.