tb_port_lane_bonding_enable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

tb_port_lane_bonding_enable β€” Enable bonding on port πŸ’…

okay so you're on the tb_port_lane_bonding_enable(9) page in the Kernel API Manual, and this whole function is giving β€œmake that port bond” main character energy ✨


✨ SYNOPSIS ✨

int tb_port_lane_bonding_enable (struct tb_port *port );

πŸŽ€ ARGUMENTS πŸŽ€

  • port β€” the port to enable. that's the whole assignment, bestie 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the tea β˜•: tb_port_lane_bonding_enable enables bonding by setting the link width of the port and the other port in case of dual link port. it's lowkey doing double duty when there's a dual link situation πŸ’…

but bestie, hear me: it does not wait for the link to actually reach the bonded state. so the caller needs to call tb_port_wait_for_link_width before enabling any paths through the link, to make sure the link is in expected state. no cap, do not skip that step 😭

⚠️ vibe check: enabling paths too early is not the move. call tb_port_wait_for_link_width first, fr fr.

πŸ”₯ RETURN πŸ”₯

0 on success, negative errno otherwise. so like, zero is the slay result; anything negative is the sad little error result πŸ˜­πŸ’€


🌈 SEE ALSO 🌈

Kernel file, right here: ./drivers/thunderbolt/switch.c πŸ’–

the whole related-function friend group, in order:


mwah πŸ’‹ this page's footer energy: source/version ./drivers/thunderbolt, date October 2026, and the page name tb_port_lane_bonding_enable(9). bye bestie, go get that bond 🫢✨

πŸ“¦ where this page comes from