drivers/thunderbolt/switch.c

1017  * enable/disable lane bonding. For that call tb_port_set_lane_bonding().
1064  * tb_port_set_lane_bonding() - Enable/disable lane bonding
1066  * @bonding: enable/disable bonding
1068  * Enables or disables lane bonding. This should be called after target
1071  * lane bonding.
1075 static int tb_port_set_lane_bonding(struct tb_port *port, bool bonding)
1088 	if (bonding)
1098  * tb_port_lane_bonding_enable() - Enable bonding on port
1101  * Enable bonding by setting the link width of the port and the other
1115 	 * Enable lane bonding for both links if not already enabled by
1134 	 * Only set bonding if the link was not already bonded. This
1135 	 * avoids the lane adapter to re-enter bonding state.
1144 	 * When lane 0 bonding is set it will affect lane 1 too so
1161  * tb_port_lane_bonding_disable() - Disable bonding on port
1164  * Disable bonding by setting the link width of the port and the
1183  * bonding has been disabled) to wait until the link actually reaches
1248  * After the link is bonded (or bonding was disabled) the port total
2897  * tb_switch_lane_bonding_enable() - Enable lane bonding
2898  * @sw: Switch to enable lane bonding
2900  * Connection manager can call this function to enable lane bonding of a
2929 		tb_port_warn(up, "failed to enable lane bonding\n");
2935 		tb_port_warn(down, "failed to enable lane bonding\n");
2948  * tb_switch_lane_bonding_disable() - Disable lane bonding
2949  * @sw: Switch whose lane bonding to disable
2951  * Disables lane bonding between @sw and parent. This can be called even
3146  * It is recommended that this is called after lane bonding is enabled.