tb_acpi_power_on_retimers(9)
β¨ tb_acpi_power_on_retimers β¨
okay bestie, welcome to the tb_acpi_power_on_retimers(9) page π
this one lives in the Kernel API Manual (section 9, fancy), and it's basically the "hey platform, wake the retimers up" button π«Ά
πΈ SYNOPSIS πΈ
int tb_acpi_power_on_retimers (struct tb_port *port );
π ARGUMENTS π
portβ the USB4 port in question. that's the one, that's our girl π¦
π DESCRIPTION π
so what it does: it calls the platform to turn on power to all the retimers behind this USB4 port. all of them. every single one. no cap β¨
once this function returns successfully, the caller can go ahead and continue with the normal retimer flows β you know, the ones specified in the USB4 spec π slay.
π important lil heads up: if this returns -EBUSY, it means the type-C port is in non-USB4/TBT mode β like, there's a non-USB4/TBT device connected. so it's giving "wrong vibe, wrong device" π
and fr fr, this should only be called if the USB4/TBT link is not up. do not come for this function when the link is already living its best life π₯
π RETURN π
0 on success, negative errno otherwise. that's it, that's the whole mood π―
π¦ SEE ALSO π¦
- Kernel file
./drivers/thunderbolt/acpi.c tb_acpi_add_links(9)tb_acpi_is_native(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_off_retimers(9)
okay that's the whole page, you ate that π
mwah! π source vibes: ./drivers/thunderbolt, dated October 2026, and yeah β that's the tb_acpi_power_on_retimers(9) girlie signing off ππ«Άπ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms